Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


In this Discussion

New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

CVE-2026-99312: KVM Guest-to-Host Escape

Comments

  • FubukiFubuki Member

    Another one?

    Thanked by 1whynotlearn
  • whynotlearnwhynotlearn Member
    edited 4:56PM

    (Hey been sometime since I talked in the forum, how are you all doing?

    Now I came across this post and I had to post it on LET. This is related to security, thus posting it at #security under the news sections but dear mods, please feel free to change it to relevant tag if its not the right one. )

    Talking about the actual CVE, how many companies are impacted by this? KVM guest to host escapes are pretty rare and there was one just sometime ago but it was considered to be rare (from what I know)

    Secondly, they seem to have done it for digitalocean droplets so I find it pretty crazy. I think that it might impact other providers as well so sharing it here for letting people and providers know and hopefully mitigate it.

    From the website:

    Mitigation

    Many cloud providers we surveyed are out of reach for one reason: they did not enable nested virtualization on AMD.

    Running KVM hosts on AMD? Update to a kernel that carries the fix.
    
    Cannot update yet? Set the nested parameter of the kvm_amd module to 0. 
    

    That turns nested virtualization off and closes this path completely.

  • @Fubuki said:
    Another one?

    Sadly yes :-(

Sign In or Register to comment.