VulnWatch by ve1ve2
medium 5.5 EPSS 0.21%

CVE-2026-99335: In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready Wait to…

Source:
NVD CVE API 2.0
Published:
Fetched:
Updated:
Affects:
linux

https://nvd.nist.gov/vuln/detail/CVE-2026-99335 ↗

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: https://git.kernel.org/stable/c/3fe5d2944e5ac3fc5073344b0982c73703332e18 https://git.kernel.org/stable/c/698f807aa8df9414fdc23d9ea454f4883b5b08ff https://git.kernel.org/stable/c/dc0cb5d30647b22a3da252a2847ed8f6afb5d567 https://git.kernel.org/stable/c/fd224f1778e13660aec4e1f51fcdaeab5794e7ee

Linked vulnerabilities (1)

CVE-2026-99335 medium 5.5 EPSS 0.21% (p12) NVDCVE.org
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

kernel: kernel: Denial of service via premature guest memory slot binding in KVM

CWE: CWE-476Aliases: CVE-2026-99272, CVE-2026-99275, CVE-2026-99308, CVE-2026-99312, CVE-2026-99314, CVE-2026-99315, CVE-2026-99316, CVE-2026-99317, CVE-2026-99318, CVE-2026-99319, CVE-2026-99320, CVE-2026-99336, CVE-2026-99345, CVE-2026-99347, CVE-2026-99348, CVE-2026-99350, CVE-2026-99363, CVE-2026-99376, CVE-2026-99377, CVE-2026-99379, CVE-2026-99382, CVE-2026-99384, CVE-2026-99387, CVE-2026-99394, CVE-2026-99426, CVE-2026-99484, CVE-2026-99496, CVE-2026-99566, CVE-2026-99567, CVE-2026-99568, CVE-2026-99569, CVE-2026-99570, CVE-2026-99573, CVE-2026-99574, CVE-2026-99575, CVE-2026-99576, CVE-2026-99577, CVE-2026-99578, CVE-2026-99579, CVE-2026-99580, CVE-2026-99582, CVE-2026-99583, CVE-2026-99587, CVE-2026-99588, CVE-2026-99589, CVE-2026-99590, CVE-2026-99591, CVE-2026-99593, CVE-2026-99594NVD: Received

Also reported by (1)