CVE Feed
— Unscored

In the Linux kernel, the following vulnerability has been resolved: KVM: guestmemfd: Gracefully handle xarray errors when binding a memslot…

CVE-2026-99473

In the Linux kernel, the following vulnerability has been resolved: KVM: guestmemfd: Gracefully handle xarray errors when binding a memslot If inserting a memslot into a guestmemfd's bindings xarray fails, propagate the error back to the caller, i.e. fail memslot creation as well. Signalling success and continuing on with memslot creation results in use-after-free, as the guestmemfd instance will remain reachable via the memslot after the file is freed (kvmgmemrelease() won't nullify the file pointer due to lack of a valid binding). Opportunistically WARN and reject binding if KVMMEMSLOTGMEMONLY is already set, partly to guard against goofs elsewhere, but mostly so that KVM doesn't need to worry about clobbering flags when unwinding on failure. Regarding the unwind, the slot must be fully prepared before inserting it into the bindings, at which point the slot becomes reachable. I.e. waiting to update the slot in order to avoid the ugly unwind isn't an option. And as part of the unwind, explicitly nullify the relevant bindings, as xarray can store a subset of entries when populating a range.

Assessment

CVSS
Not yet scored
Severity
Unscored
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
19 November 2026
Last updated
19 November 2026
Affected
Linux · Linux
Assigner
Linux

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99473