Public vulnerability disclosure

CVE-2026-99473

KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot

published

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.

Technical severity7.0 highCVSS 3.1 · CNA: Linux
Published2026-11-19Source updated 2026-11-22
Collected2026-11-223 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < 2cfc1ccf67ffe96811c816d27d44128c5d5833ec (affected, git)
≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < 1706461eb1af814366b6d0ab413edd0876bd8033 (affected, git)
≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < 2fa83c615f8dbb240b262265e788b120b6384e7b (affected, git)
≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < e6ecb88711d93b9e014532f17d3d29b57e80932c (affected, git)
Other versions: unaffected
CNA: Linux
Linux
Linux
6.8 (affected)
≥ 0; < 6.8 (unaffected, semver)
≥ 6.12.117; ≤ 6.12.* (unaffected, semver)
≥ 6.18.63; ≤ 6.18.* (unaffected, semver)
≥ 7.3.2; ≤ 7.3.* (unaffected, semver)
≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 7.0
high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HCNA: Linux
3.1 / 7.0
high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HNVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide