CVE-2026-99420: Linux kernel · ovl: check that the parents of volatile/dirty are dirs
Source GCVE Database
Not known to be exploited · fixed in e34d2ef818e4c7676d8d8e1bf43e6a1ed39efb2a : patch Linux kernel soon.
Data as of 19 Nov 2026, 17: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 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 has been implemented that returns an error when a non-directory entry is encountered where a directory is expected during overlayfs volatile/dirty lookups. Users should apply the official kernel patch or update to a fixed kernel version once available. Until then, avoid mounting overlayfs with the volatile option in unprivileged user namespaces to mitigate risk.
Description
CVE-2026-99420 is a Linux kernel vulnerability in the overlayfs subsystem related to handling of volatile and dirty directories. An unprivileged user can cause a kernel crash by mounting overlayfs with the volatile option in a user namespace while another process creates a symlink that disrupts expected directory structures. The flaw occurs because the kernel does not properly verify that parents of volatile/dirty entries are directories, leading to a NULL pointer dereference during lookup. The issue is fixed by adding a check that returns an error when a non-directory entry is encountered where a directory is expected.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99420 (opens in a new tab)
- git.kernel.org/stable/c/3bf6fda63259692331d21392c3f7c0c02594dae5 (opens in a new tab)
- git.kernel.org/stable/c/68439a05ed529a8b0350f8c6ff3618ff4a8d972d (opens in a new tab)
- git.kernel.org/stable/c/a343bd631606d9d508808fca272e1e482ed6c61f (opens in a new tab)
- git.kernel.org/stable/c/e34d2ef818e4c7676d8d8e1bf43e6a1ed39efb2a (opens in a new tab)