CVE-2026-99692: Linux kernel · ocfs2: stop recovery before shutting down local allocators
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 781991ddd2c4b6f003b7bdef6b7aae6db722707d : patch Linux kernel soon.
Data as of 20 Nov 2026, 06:38 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 781991ddd2c4b6f003b7bdef6b7aae6db722707d, 126429e2f503ade63502978beb0c519066442250, 47997a43d33fcb3d4a87249bfd8ab07ede119fa3 +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 781991ddd2c4b6f003b7bdef6b7aae6db722707d, 126429e2f503ade63502978beb0c519066442250, 47997a43d33fcb3d4a87249bfd8ab07ede119fa3 or 22c123334f3c4effc0b46923da2938e54ad3075b.
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 indicated by multiple fixed commits. Users should update to a Linux kernel version that includes these fixes. Since this is a kernel-level issue, applying the official kernel patches or upgrading to a fixed kernel release is the recommended mitigation.
Description
CVE-2026-99692 is a use-after-free vulnerability in the ocfs2 filesystem code of the Linux kernel. It occurs due to improper ordering in stopping recovery processes and shutting down local allocators during unmount, which can lead to use of freed memory. The issue was detected by KASAN and fixed by ensuring recovery producers are stopped and completion work drained before local allocators are shut down.
References
- git.kernel.org/stable/c/22c123334f3c4effc0b46923da2938e54ad3075b (opens in a new tab)
- git.kernel.org/stable/c/781991ddd2c4b6f003b7bdef6b7aae6db722707d (opens in a new tab)
- git.kernel.org/stable/c/47997a43d33fcb3d4a87249bfd8ab07ede119fa3 (opens in a new tab)
- git.kernel.org/stable/c/126429e2f503ade63502978beb0c519066442250 (opens in a new tab)