CVE-2026-99473
Severity unknownNo known exploitationFix availableKVM: guest_memfd: Gracefully handle xarray errors when binding a memslot
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 6% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from a7800aa80ea4d5356b8474c2302812e9d4926fa6 before 2cfc1ccf67ffe96811c816d27d44128c5d5833ec | 2cfc1ccf67ffe96811c816d27d44128c5d5833ec | CVE Program |
| Linux | Linux | from a7800aa80ea4d5356b8474c2302812e9d4926fa6 before 1706461eb1af814366b6d0ab413edd0876bd8033 | 1706461eb1af814366b6d0ab413edd0876bd8033 | CVE Program |
| Linux | Linux | from a7800aa80ea4d5356b8474c2302812e9d4926fa6 before 2fa83c615f8dbb240b262265e788b120b6384e7b | 2fa83c615f8dbb240b262265e788b120b6384e7b | CVE Program |
| Linux | Linux | from a7800aa80ea4d5356b8474c2302812e9d4926fa6 before e6ecb88711d93b9e014532f17d3d29b57e80932c | e6ecb88711d93b9e014532f17d3d29b57e80932c | CVE Program |
| Linux | Linux | 6.8 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.63 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.8 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/1706461eb1af814366b6d0ab413edd0876bd8033 (opens in a new tab)
- https://git.kernel.org/stable/c/2cfc1ccf67ffe96811c816d27d44128c5d5833ec (opens in a new tab)
- https://git.kernel.org/stable/c/2fa83c615f8dbb240b262265e788b120b6384e7b (opens in a new tab)
- https://git.kernel.org/stable/c/e6ecb88711d93b9e014532f17d3d29b57e80932c (opens in a new tab)