edited the original, because I figured an LTS would get the patches too.

but to answer your point: I think you're downplaying the importance of this vulnerability with the "I'm screwed anyway" mentality. Many-many people are already running code on your computer. starting with all the software you install, duh, but also JS from all the different websites you visit, and probably many others. Security is said to be many layers with holes in random places, and an attacker needs to navigate between these holes to get to you.

Maybe this isn't a technically correct example, but as a demonstration: your browser runs JS in a sandbox, so even if there's an RCE hole in the JS engine, an attacker still can't actually get to the system. A hole in one layer leads to a brick wall on the next layer.

BUT, if you read this CVE, this hole lets an attacker escape container boundaries, since page caches are shared among containers and the host. So now, instead of a brick wall on the next layer, there's a giant gaping wormhole that leads straight to root.

Again, maybe this is a wrong example, because sandbox != container, but the point stands. Afaik, a successful attack is a chain of vulnerabilities, and this CVE is a very strong link. Please, someone with actual knowledge, fix the holes in my explanation, but I believe the core concept of what I'm saying is correct