CVE-2026-99420: Linux kernel · ovl: check that the parents of volatile/dirty are dirs
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e34d2ef818e4c7676d8d8e1bf43e6a1ed39efb2a : patch Linux kernel soon.
Data as of 19 Nov 2026, 14:52 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 e34d2ef818e4c7676d8d8e1bf43e6a1ed39efb2a, a343bd631606d9d508808fca272e1e482ed6c61f, 68439a05ed529a8b0350f8c6ff3618ff4a8d972d +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 e34d2ef818e4c7676d8d8e1bf43e6a1ed39efb2a, a343bd631606d9d508808fca272e1e482ed6c61f, 68439a05ed529a8b0350f8c6ff3618ff4a8d972d or 3bf6fda63259692331d21392c3f7c0c02594dae5.
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. Users should update to the fixed kernel versions identified by the commits e34d2ef818e4c7676d8d8e1bf43e6a1ed39efb2a, a343bd631606d9d508808fca272e1e482ed6c61f, 68439a05ed529a8b0350f8c6ff3618ff4a8d972d, and 3bf6fda63259692331d21392c3f7c0c02594dae5. No additional mitigation steps are indicated.
Description
CVE-2026-99420 is a Linux kernel vulnerability in the overlayfs component where an unprivileged user can cause a kernel crash by mounting overlayfs with the volatile option. The issue arises because the kernel does not properly verify that the parents of volatile/dirty dentries are directories, leading to a NULL pointer dereference during lookup operations. This flaw was fixed by ensuring that a non-directory entry is not treated as a directory during overlayfs volatile mounts.
References
- git.kernel.org/stable/c/a343bd631606d9d508808fca272e1e482ed6c61f (opens in a new tab)
- git.kernel.org/stable/c/68439a05ed529a8b0350f8c6ff3618ff4a8d972d (opens in a new tab)
- git.kernel.org/stable/c/3bf6fda63259692331d21392c3f7c0c02594dae5 (opens in a new tab)
- git.kernel.org/stable/c/e34d2ef818e4c7676d8d8e1bf43e6a1ed39efb2a (opens in a new tab)