CVE-2026-99473
KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot
What happened?
In the Linux kernel, the following vulnerability has been resolved:
KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot
If inserting a memslot into a guest_memfd'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 guest_memfd instance will remain reachable via the memslot after the file is freed (kvm_gmem_release() won't nullify the file pointer due to lack of a valid binding).
Opportunistically WARN and reject binding if KVM_MEMSLOT_GMEM_ONLY 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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: a7800aa80ea4d5356b8474c2302812e9d4926fa6 to < 2cfc1ccf67ffe96811c816d27d44128c5d5833ec; affected: a7800aa80ea4d5356b8474c2302812e9d4926fa6 to < 1706461eb1af814366b6d0ab413edd0876bd8033; affected: a7800aa80ea4d5356b8474c2302812e9d4926fa6 to < 2fa83c615f8dbb240b262265e788b120b6384e7b; affected: a7800aa80ea4d5356b8474c2302812e9d4926fa6 to < e6ecb88711d93b9e014532f17d3d29b57e80932c | See vendor advisory |
| LinuxLinux | affected: 6.8; unaffected: 0 to < 6.8; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.63 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99473
- https://git.kernel.org/stable/c/2cfc1ccf67ffe96811c816d27d44128c5d5833ec
- https://git.kernel.org/stable/c/1706461eb1af814366b6d0ab413edd0876bd8033
- https://git.kernel.org/stable/c/2fa83c615f8dbb240b262265e788b120b6384e7b
- https://git.kernel.org/stable/c/e6ecb88711d93b9e014532f17d3d29b57e80932c