CVE-2026-99429: Linux kernel · ocfs2: pin refcount trees before dropping the lookup lock
Source GCVE Database
Not known to be exploited · fixed in ce7b46556af15642a1e9f8d0c596022dd7cfb4a7 : patch Linux kernel soon.
Data as of 19 Nov 2026, 17:49 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 ce7b46556af15642a1e9f8d0c596022dd7cfb4a7, 8c714a074074af7ae59233c1fa6ef9d7aa710462, 7ff4f020f7b03fddd529735f0b61ac0a8dd92c9e +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 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 18 Nov 2026.
What to do
Upgrade Linux kernel to ce7b46556af15642a1e9f8d0c596022dd7cfb4a7, 8c714a074074af7ae59233c1fa6ef9d7aa710462, 7ff4f020f7b03fddd529735f0b61ac0a8dd92c9e or 2d9e864c234469dc7f56ea974f8269d251441e6a.
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 that changes ocfs2_get_refcount_tree() to take the operation reference before releasing the osb_lock, preventing the refcount tree from being freed prematurely. Users should apply the official kernel patches that address this issue. No additional mitigations are indicated by the vendor advisory.
Description
A use-after-free vulnerability exists in the ocfs2 filesystem implementation in the Linux kernel due to improper handling of refcount trees. The issue arises because a refcount tree pointer can be freed and reused concurrently while still being accessed, leading to potential memory corruption. This flaw was identified through KASAN reports and involves race conditions between local operations on different inodes. The vulnerability has been resolved by ensuring the operation reference is taken before releasing the lookup lock, preventing premature freeing of the refcount tree.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99429 (opens in a new tab)
- git.kernel.org/stable/c/2d9e864c234469dc7f56ea974f8269d251441e6a (opens in a new tab)
- git.kernel.org/stable/c/7ff4f020f7b03fddd529735f0b61ac0a8dd92c9e (opens in a new tab)
- git.kernel.org/stable/c/8c714a074074af7ae59233c1fa6ef9d7aa710462 (opens in a new tab)
- git.kernel.org/stable/c/ce7b46556af15642a1e9f8d0c596022dd7cfb4a7 (opens in a new tab)