# CVE-2026-99473: KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot

Status: published. Published: 2026-11-19. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < 2cfc1ccf67ffe96811c816d27d44128c5d5833ec (affected, git); ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < 1706461eb1af814366b6d0ab413edd0876bd8033 (affected, git); ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < 2fa83c615f8dbb240b262265e788b120b6384e7b (affected, git); ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6; < e6ecb88711d93b9e014532f17d3d29b57e80932c (affected, git). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.20%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

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

## References

- https://git.kernel.org/stable/c/2cfc1ccf67ffe96811c816d27d44128c5d5833ec (CNA: Linux)

- https://git.kernel.org/stable/c/1706461eb1af814366b6d0ab413edd0876bd8033 (CNA: Linux)

- https://git.kernel.org/stable/c/2fa83c615f8dbb240b262265e788b120b6384e7b (CNA: Linux)

- https://git.kernel.org/stable/c/e6ecb88711d93b9e014532f17d3d29b57e80932c (CNA: Linux)

- https://git.kernel.org/stable/c/1706461eb1af814366b6d0ab413edd0876bd8033 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/2cfc1ccf67ffe96811c816d27d44128c5d5833ec (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/2fa83c615f8dbb240b262265e788b120b6384e7b (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/e6ecb88711d93b9e014532f17d3d29b57e80932c (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99473; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99473; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99473; retrieved 2026-11-22; source updated Not reported

Revision: 8815f212e8b19ffe4318b909c087c5d71dfc781aae36eab9ce59abe3581d0f96

Canonical: https://y2.dev/cve/CVE-2026-99473

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.