CVE-2026-99730: Linux kernel · mm/filemap: finish fault cleanup before dropping the fault lock
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f1c149e651fd55edc0769b76ebd688ae6cbd48f0 : patch Linux kernel soon.
Data as of 20 Nov 2026, 06:34 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f1c149e651fd55edc0769b76ebd688ae6cbd48f0, efa7aec3f30d79a7d35edd219c6f49235f331013, 97156a6c355c21f7122421915f05461bd11699a4 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel as identified by the fixed commit hashes. Users and administrators should update to the patched kernel versions containing these fixes. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's memory management subsystem (mm/filemap) involves improper handling of fault cleanup before dropping the fault lock. This flaw can lead to a race condition where a concurrent munmap() frees a mapping prematurely, potentially causing use-after-free issues. The issue has been fixed by deferring the dropping of the fault lock until after necessary cleanup is complete.
References
- git.kernel.org/stable/c/efa7aec3f30d79a7d35edd219c6f49235f331013 (opens in a new tab)
- git.kernel.org/stable/c/f1c149e651fd55edc0769b76ebd688ae6cbd48f0 (opens in a new tab)
- git.kernel.org/stable/c/8500faaa6ef7b4489294f2bf98c9017ee009986c (opens in a new tab)
- git.kernel.org/stable/c/97156a6c355c21f7122421915f05461bd11699a4 (opens in a new tab)