Birbla

Discussion summary

A recent CVE-2026-53359 vulnerability affects KVM/x86, raising security concerns in resource sharing. Discussions highlight trade-offs between cost, management, and security in server and container setups.

What the discussion says

  • Sharing resources reduces costs but increases security risks.
  • Running dedicated servers offers more security but at higher costs.
  • Managing larger scale deployments becomes more complex.
  • Some users prefer affordable hosting options like Hetzner.
  • Linux device files can be exploited due to permissions.
“Sharing resources reduces costs but increases security risks.”
— rballpug
“Managing larger scale deployments becomes more complex.”
— antonvs

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • xenchads dabbing on kvmvirgins once again
    by anonym29
  • > LPE: On distributions such as RHEL, /dev/kvm is world-writable (0666), so an unprivileged user can also use this vulnerability as a reliable LPE to gain root.

    Why on Linux device files are accessible by untrusted applications?

    by codedokode
  • Some of the comments here talk about the risk this poses for multi tenant vm providers.

    Wouldn't this also be a risk for people using VMs to sandbox untrusted code running on trusted hosts?

    by CoastalCoder
  • Anyone know if "-cpu ${CPU},vmx=off,svm=off" in QEMU is a safe workaround for this?

    (To disable nested virtualization on a per-VM basis. Only against exploitation from within that specific VM, obviously does nothing against users with access to /dev/kvm on the host.)

    by eqvinox
  • hey, here's a good rule of thumb.

    If you share resources, that reduces costs, but increases security risks.

    choose whether to share a filesystem, an OS, a kernel, hardware, or just use a dedicated server.

    The economics of sharing resources are all in a tiny sliver of the budget spectrum, the shoestring budget range :

    0-1$/mo: serverless

    1$-5$/mo containers

    5$-200$/mo Virtual Machine(s)

    200$-1Billion$/month , at least one dedicated server

    So if your hourly is worth anywhere upwards of 5$/hr, and your project has any semblance of seriousness, just use a dedicated server, and avoid a whole class of LPE vulnerabilities just to save some $.

    Businesses have expenses, let's stop pretending that all of these non dedicated server infrastructures are serious. Shell out 200$/month or stick to hobby status.

    No, I don't sell dedicated servers, but I should

    by TZubiri
  • "If you operate an x86 KVM host that accepts multi-tenant guests and supports nested virtualization, or use an instance on top of one"

    does this mean that you must have nested virtualization enabled to br vulnerable. does disabling this feature in the host os or bios, make you immune to this bug?

    by br0ceph
  • Nested virt on x86 is curiously painful; you'd kind of think each layer would be isolated, so that the L0 (hardware) would only have to worry about it's VM (L1), and L1 would have to worry about it's VM (L2); but nope - the L0 top level hypervisor sees faults from the L2 and has to figure out that they are actually L2 not L0. IMHO the extra complexity (and historical flakiness of it) - makes me say that enabling nesting is a bad idea for public VM hosts.
    by trebligdivad
  • The full write up is here: [0].

    This is a very nasty vulnerability and risks any service that uses and allows nested x86 virtualization features at risk. Including those running VMs as a service.

    > Running the PoC inside a guest VM can trigger a host kernel panic. A full escape exploit that works in a controlled environment also exists, but it is not released at this time and is planned to be released in the very distant future.

    The first commit that introduced this vulnerability was in 2010. [1] So it was undiscovered for 16 years until now [2].

    It was only a matter of time that a vulnerability in KVM would appear. This one is really not good as it is the first KVM guest-to-host exploit working on both AMD and Intel.

    [0] https://github.com/V4bel/Januscape/blob/main/assets/write-up...

    [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

    [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

    by rvz

Explore Birbla archives