Skip to main content
VulnerabilityPublished

CVE-2026-99730: Linux kernel · mm/filemap: finish fault cleanup before dropping the fault lock

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99730· High

Not known to be exploited · fixed in f1c149e651fd55edc0769b76ebd688ae6cbd48f0 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f1c149e651fd55edc0769b76ebd688ae6cbd48f0, efa7aec3f30d79a7d35edd219c6f49235f331013, 97156a6c355c21f7122421915f05461bd11699a4 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to f1c149e651fd55edc0769b76ebd688ae6cbd48f0, efa7aec3f30d79a7d35edd219c6f49235f331013, 97156a6c355c21f7122421915f05461bd11699a4 or 8500faaa6ef7b4489294f2bf98c9017ee009986c.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 730633f0b7f951726e87f912a6323641f674ae34, < f1c149e651fd55edc0769b76ebd688ae6cbd48f0
Fixed in
  • f1c149e651fd55edc0769b76ebd688ae6cbd48f0
LinuxLinuxAffected
  • ≥ 730633f0b7f951726e87f912a6323641f674ae34, < efa7aec3f30d79a7d35edd219c6f49235f331013
Fixed in
  • efa7aec3f30d79a7d35edd219c6f49235f331013
LinuxLinuxAffected
  • ≥ 730633f0b7f951726e87f912a6323641f674ae34, < 97156a6c355c21f7122421915f05461bd11699a4
Fixed in
  • 97156a6c355c21f7122421915f05461bd11699a4
LinuxLinuxAffected
  • ≥ 730633f0b7f951726e87f912a6323641f674ae34, < 8500faaa6ef7b4489294f2bf98c9017ee009986c
Fixed in
  • 8500faaa6ef7b4489294f2bf98c9017ee009986c
LinuxLinuxAffected
  • =5.15
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/filemap: finish fault cleanup before dropping the fault lock On a retried fault, a fatal signal interrupting the folio lock wait makes lock_folio_maybe_drop_mmap() drop the fault lock without pinning the file. However, filemap_fault() may still need to release mapping->invalidate_lock. A concurrent munmap() can release the last file reference and free the mapping before that unlock. Defer dropping the fault lock to filemap_fault()'s retry cleanup, after releasing invalidate_lock. If the fault lock was already dropped for I/O, release the existing file reference instead. Keep the fault lock held for FAULT_FLAG_RETRY_NOWAIT as before.

References

Community reviews

Loading reviews…