CVE-2026-99336
KVM: guest_memfd: take the invalidate lock when unbinding a dying file
No exploitation reported by the sources we read.
- Published2026-11-19
- Fixed in7.3.2 · 6.18.64 · 6.18 · 6.12.118
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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: take the invalidate lock when unbinding a dying file kvm_gmem_unbind() takes mapping->invalidate_lock only if the get_file_active() succeeds. When the guest_memfd file is dying, its reference count is already zero so get_file_active fails and the binding is removed without holding the invalidate lock. kvm_gmem_invalidate_{start,end}() checks f->bindings independently to decide whether to begin or end KVM MMU invalidation. So, the bindings must therefore remain stable between the two calls. Otherwise, unbind can remove a binding after start increments mmu_invalidate_in_progress, but before end finds the binding and decrements it. Example, unbind race with memory failure: CPU 0: memory failure CPU 1: memslot delete ---------------------------------- --------------------------- (guest_memfd file is dying) kvm_gmem_error_folio() kvm_gmem_invalidate_start() finds binding mmu_invalidate_in_progress++ kvm_gmem_unbind() get_file_active() fails removes binding kvm_gmem_invalidate_end() no binding found counter stays elevated mmu_invalidate_retry() then returns 1 forever, so guest page faults retry without ever installing a mapping and the guest hangs. Remove the distinction between live and dying files in the unbind path. Always use slot->gmem.file and take the invalidate lock when it's non-NULL. Normal unbind callers hold slots_lock, which prevents release from clearing the pointer or freeing the file state until unbind completes. Final VM teardown can only see a NULL pointer because guest_memfd pins the KVM until release has cleared all bindings.
Timeline
dates in UTC- 2026-11-1914:21CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.19.0, < 7.3.2 | 7.3.2 | OSV |
| 6.18 | ≥ 6.18.0, < 6.18.64 | 6.18.64 | OSV |
| 6.x | ≥ 6.17.9, < 6.18 | 6.18 | OSV |
| 6.12 | ≥ 6.12.59, < 6.12.118 | 6.12.118 | OSV |
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- ≥ a8ac2bd0f98e1a230f1eb3260fa552bf2ef1753b, < 4ae4316682cdc78d8f5a856ab0712a8281f211cafixed in 4ae4316682cdc78d8f5a856ab0712a8281f211cagit
- ≥ ae431059e75d36170a5ae6b44cc4d06d43613215, < 3af94f4e3526efdf52d84d7ba8d9fb8e8facb93afixed in 3af94f4e3526efdf52d84d7ba8d9fb8e8facb93agit
- ≥ ae431059e75d36170a5ae6b44cc4d06d43613215, < 024be82ac4c4df650cc6daca6d7db79daee95470fixed in 024be82ac4c4df650cc6daca6d7db79daee95470git
- ≥ ae431059e75d36170a5ae6b44cc4d06d43613215, < 0ee2c883b62deb74d8c43007e8049dc006d3a2fbfixed in 0ee2c883b62deb74d8c43007e8049dc006d3a2fbgit
- = 393893693a523e053f84d69320d090b93503f79fno fix statedgit
- ≥ 6.12.59, < 6.12.118fixed in 6.12.118semver
- ≥ 6.17.9, < 6.18fixed in 6.18semver
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 6.18no fix stated
Not affected < 6.18 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 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.118-1
- 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-99336 Red Hat Product Security
kernel: kernel: Denial of Service via race condition in KVM guest memory unbinding
Fix
- Update Linux kernel to 7.3.2 · 6.18.64 · 6.18 · 6.12.118
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-20
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-22
- CNACVSS 3.172026-11-22
- FIRST EPSSEPSS score0.2 %2026-11-21
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-130234same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-gh4c-w75c-262gsame flawGitHub Advisory Database · CC-BY-4.0
- DSA-6652-1advisory covering several CVEsDebian · LicenseRef-unstated
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-gh4c-w75c-262g
Frequently asked questions
What is CVE-2026-99336?
Is CVE-2026-99336 actively exploited?
What is the CVSS score for CVE-2026-99336?
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
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-gh4c-w75c-262g
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0