CVE-2026-99335
What it is
In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready Wait to bind a memslot to a guest_memfd instance until *after* the memslot is fully prepared, as creating the binding in guest_memfd will effectively expose the memslot to readers. As pointed out by Sashiko, binding the memslot before it's ready to be exposed to the rest of the world can break various memslot assumption and rules. E.g. x86 could observe a NULL rmap pointer if a PUNCH_HOLE hit the guest_memfd after the binding was created, but before KVM made it through kvm_prepare_memory_region().
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 698f807aa8df9414fdc23d9ea454f4883b5b08ff
- Linux < dc0cb5d30647b22a3da252a2847ed8f6afb5d567
- Linux < fd224f1778e13660aec4e1f51fcdaeab5794e7ee
- Linux < 3fe5d2944e5ac3fc5073344b0982c73703332e18
- Linux 6.8
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99335.md and follow it. Check whether this project is affected by CVE-2026-99335. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.