Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99473

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

No exploitation reported by the sources we read.

  • Published2026-11-19
  • Fixed in7.3.2 · 6.18.63 · 6.12.117

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1914:43CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.27.3.2
6.x≥ 6.13.0, < 6.18.636.18.63
6.x≥ 6.8.0, < 6.12.1176.12.117

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < 2cfc1ccf67ffe96811c816d27d44128c5d5833ecfixed in 2cfc1ccf67ffe96811c816d27d44128c5d5833ecgit
    • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < 1706461eb1af814366b6d0ab413edd0876bd8033fixed in 1706461eb1af814366b6d0ab413edd0876bd8033git
    • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < 2fa83c615f8dbb240b262265e788b120b6384e7bfixed in 2fa83c615f8dbb240b262265e788b120b6384e7bgit
    • ≥ a7800aa80ea4d5356b8474c2302812e9d4926fa6, < e6ecb88711d93b9e014532f17d3d29b57e80932cfixed in e6ecb88711d93b9e014532f17d3d29b57e80932cgit
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.8no fix stated

    Not affected < 6.8 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.63, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-19

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxDebian:14all versions · fixed in 7.3.3-1
  • linuxDebian:13all versions · fixed in 6.12.117-1
  • linux-6.12Debian:12all versions · fixed in 6.12.117-1~deb12u1
  • linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed

Vendor advisories

  • CVE-2026-99473 Red Hat Product Security

    kernel: kernel: KVM: Use-after-free via guest memory slot binding failure

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.2 · 6.18.63 · 6.12.117

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-19
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-4rww-grmf-xvgg

Frequently asked questions

What is CVE-2026-99473?

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.

Is CVE-2026-99473 actively exploited?

Active exploitation of CVE-2026-99473 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99473?

CVE-2026-99473 has a CVSS v3 base score of 7 (High severity), with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record