Skip to content
Threat Brief

← All advisories

CVE-2026-99336

Severity unknownNo known exploitationFix available

KVM: guest_memfd: take the invalidate lock when unbinding a dying file

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 12% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

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

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 6.12.59 before 6.12.1186.12.118CVE Program
LinuxLinuxfrom 6.17.9 before 6.186.18CVE Program
LinuxLinuxfrom a8ac2bd0f98e1a230f1eb3260fa552bf2ef1753b before 4ae4316682cdc78d8f5a856ab0712a8281f211ca4ae4316682cdc78d8f5a856ab0712a8281f211caCVE Program
LinuxLinuxfrom ae431059e75d36170a5ae6b44cc4d06d43613215 before 024be82ac4c4df650cc6daca6d7db79daee95470024be82ac4c4df650cc6daca6d7db79daee95470CVE Program
LinuxLinuxfrom ae431059e75d36170a5ae6b44cc4d06d43613215 before 3af94f4e3526efdf52d84d7ba8d9fb8e8facb93a3af94f4e3526efdf52d84d7ba8d9fb8e8facb93aCVE Program
LinuxLinuxfrom ae431059e75d36170a5ae6b44cc4d06d43613215 before 0ee2c883b62deb74d8c43007e8049dc006d3a2fb0ee2c883b62deb74d8c43007e8049dc006d3a2fbCVE Program
LinuxLinux393893693a523e053f84d69320d090b93503f79fNot documentedCVE Program
LinuxLinux6.18Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.18Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references