Skip to main content
VulnerabilityPublished

CVE-2026-99335: Linux kernel · KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fd224f1778e13660aec4e1f51fcdaeab5794e7ee : update Linux kernel when convenient.

Data as of 19 Nov 2026, 14:34 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in fd224f1778e13660aec4e1f51fcdaeab5794e7ee, dc0cb5d30647b22a3da252a2847ed8f6afb5d567, 698f807aa8df9414fdc23d9ea454f4883b5b08ff +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to fd224f1778e13660aec4e1f51fcdaeab5794e7ee, dc0cb5d30647b22a3da252a2847ed8f6afb5d567, 698f807aa8df9414fdc23d9ea454f4883b5b08ff or 3fe5d2944e5ac3fc5073344b0982c73703332e18.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < fd224f1778e13660aec4e1f51fcdaeab5794e7ee
Fixed in
  • fd224f1778e13660aec4e1f51fcdaeab5794e7ee
LinuxLinuxAffected
  • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < dc0cb5d30647b22a3da252a2847ed8f6afb5d567
Fixed in
  • dc0cb5d30647b22a3da252a2847ed8f6afb5d567
LinuxLinuxAffected
  • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < 698f807aa8df9414fdc23d9ea454f4883b5b08ff
Fixed in
  • 698f807aa8df9414fdc23d9ea454f4883b5b08ff
LinuxLinuxAffected
  • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < 3fe5d2944e5ac3fc5073344b0982c73703332e18
Fixed in
  • 3fe5d2944e5ac3fc5073344b0982c73703332e18
LinuxLinuxAffected
  • =6.8
Fixed in–

Description

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().

References

Community reviews

Loading reviews…