CVE-2026-99422: Linux kernel · ovl: use the pinned upper dir in ovl_fix_origin()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b219cdaea16b2f3e8e13a63662d462addd8a2cd0 : patch Linux kernel soon.
Data as of 19 Nov 2026, 14:51 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 b219cdaea16b2f3e8e13a63662d462addd8a2cd0, 77c9b481faacf46b9d9282ffaa71afbac7acf819, 17a540e65e567c8e4dd165a3ce5b592842ba5ab5 +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 b219cdaea16b2f3e8e13a63662d462addd8a2cd0, 77c9b481faacf46b9d9282ffaa71afbac7acf819, 17a540e65e567c8e4dd165a3ce5b592842ba5ab5 or 4f61ff2ebfb3d2967b83b6a4d456242244d5a61f.
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 and has been applied in the Linux kernel commits identified by hashes b219cdaea16b2f3e8e13a63662d462addd8a2cd0, 77c9b481faacf46b9d9282ffaa71afbac7acf819, 17a540e65e567c8e4dd165a3ce5b592842ba5ab5, and 4f61ff2ebfb3d2967b83b6a4d456242244d5a61f. Users and administrators should update to a Linux kernel version including these fixes to remediate the issue.
Description
CVE-2026-99422 is a vulnerability in the Linux kernel overlay filesystem (ovl) where renames made directly on the upper filesystem during a lookup can crash the kernel. The issue arises because ovl_fix_origin() uses the upper directory's parent dentry without proper reference counting, leading to a use-after-free condition when multiple renames and removals occur concurrently. This has been fixed by changing the code to use the pinned upper directory dentry held by the overlay parent.
References
- git.kernel.org/stable/c/17a540e65e567c8e4dd165a3ce5b592842ba5ab5 (opens in a new tab)
- git.kernel.org/stable/c/b219cdaea16b2f3e8e13a63662d462addd8a2cd0 (opens in a new tab)
- git.kernel.org/stable/c/77c9b481faacf46b9d9282ffaa71afbac7acf819 (opens in a new tab)
- git.kernel.org/stable/c/4f61ff2ebfb3d2967b83b6a4d456242244d5a61f (opens in a new tab)