Bug 2576671 (CVE-2026-99335) - CVE-2026-99335 kernel: kernel: Denial of service via premature guest memory slot binding in KVM
Summary: CVE-2026-99335 kernel: kernel: Denial of service via premature guest memory s...
Keywords:
Status: NEW
Alias: CVE-2026-99335
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-19 14:32 UTC by OSIDB Bzimport
Modified: 2026-11-19 15:46 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-19 14:32:34 UTC
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().


Note You need to log in before you can comment on or make changes to this bug.