CVE-2026-99732: Linux kernel · mm/filemap: read mapping->a_ops->free_folio under i_lock
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to dc24e273244e9d712257d5a6c20a32c7f5ca84e6 or 842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e when convenient.
Data as of 20 Nov 2026, 06:34 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in dc24e273244e9d712257d5a6c20a32c7f5ca84e6, 842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e
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 dc24e273244e9d712257d5a6c20a32c7f5ca84e6 or 842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e.
Affected software
| Product | 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 commits dc24e273244e9d712257d5a6c20a32c7f5ca84e6 and 842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e. Users and administrators should update to a Linux kernel version that includes these fixes. No additional mitigation is required as the patch addresses the root cause by ensuring proper locking and reference handling.
Description
A use-after-free vulnerability in the Linux kernel's memory management subsystem (mm/filemap) was identified and fixed. The flaw involves reading the mapping->a_ops->free_folio pointer after the inode has been freed, due to improper locking and reference handling. This can occur when filemap_remove_folio() accesses the mapping after the inode is evicted and freed concurrently. The issue was found by code inspection and has not been reproduced in the wild. The fix involves ensuring the free_folio callback is loaded while holding the i_lock to prevent use-after-free conditions.