CVE-2026-98985: Linux kernel · namespace: check the mounts before reading their parents in pivot_root()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e3aba6900483f64e6c9eb328150dd633b7d36c1c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e3aba6900483f64e6c9eb328150dd633b7d36c1c, a56d4f8f8f4c5d9ac339d5c03a9d90eecd3697fc, 6b7c001eb5857fa09041f47673666060a2e5fc1c +3
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel version 4.1 and related commits. Users should upgrade to Linux kernel version 4.1 or later to remediate this vulnerability. No additional mitigation actions are required beyond applying the official patch.
Description
CVE-2026-98985 is a vulnerability in the Linux kernel's pivot_root() function where mounts are not properly checked before reading their parent mounts. This can lead to a use-after-free condition when new_root refers to a mount that has been unmounted but kept alive by a file descriptor. The issue is resolved by ensuring both mounts are verified to be in the caller's namespace before accessing their parents, preventing invalid memory reads. The fix returns EINVAL for invalid cases, preventing further errors.
References
- git.kernel.org/stable/c/a56d4f8f8f4c5d9ac339d5c03a9d90eecd3697fc (opens in a new tab)
- git.kernel.org/stable/c/3c2441e21c3df867e4131e0ff784ecdb3a7a55f8 (opens in a new tab)
- git.kernel.org/stable/c/e3aba6900483f64e6c9eb328150dd633b7d36c1c (opens in a new tab)
- git.kernel.org/stable/c/3dad2330c89343ba083cf7868779083fd5fbe0fe (opens in a new tab)
- git.kernel.org/stable/c/6b7c001eb5857fa09041f47673666060a2e5fc1c (opens in a new tab)