CVE-2026-98985: namespace: check the mounts before reading their parents in pivot_root()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 3184a2fda996af8fcd6def36020ec023c6279015, 3c2441e21c3df867e4131e0ff784ecdb3a7a55f8, 3dad2330c89343ba083cf7868779083fd5fbe0fe; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3184a2fda996af8fcd6def36020ec023c6279015, 3c2441e21c3df867e4131e0ff784ecdb3a7a55f8, 3dad2330c89343ba083cf7868779083fd5fbe0fe; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: namespace: check the mounts before reading their parents in pivot_root() path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace. But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards: pivot_root() close(fd), last ref on the parent ------------ --------------------------------- ex_parent = new_mnt->mnt_parent mntput_no_expire_slowpath() __umount_mnt(new_mnt) cleanup_mnt() call_rcu() IS_MNT_SHARED(ex_parent) BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840 Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157 path_pivot_root+0xf1a/0x1840 __x64_sys_pivot_root+0x165/0x190 The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 ("statmount: read the parent of an unmounted mount under mount_lock") fixed for statmount(). Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.
- Published
- Oct 23, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 84b78514033ff22c443473214ab6d0508394cf7a, 4.1affected
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before 43fd2e2ec66e6db26b6ea3e9e7a4c1018455e1b0affected · git
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before 5b5f8d0895cfa9f781ce107225d578897203444faffected · git
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before 3184a2fda996af8fcd6def36020ec023c6279015affected · git
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before a56d4f8f8f4c5d9ac339d5c03a9d90eecd3697fcaffected · git
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before 3c2441e21c3df867e4131e0ff784ecdb3a7a55f8affected · git
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before e3aba6900483f64e6c9eb328150dd633b7d36c1caffected · git
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before 3dad2330c89343ba083cf7868779083fd5fbe0feaffected · git
- e0c9c0afd2fc958ffa34b697972721d81df8a56f and later · before 6b7c001eb5857fa09041f47673666060a2e5fc1caffected · git
- 4.0.2 and later · before 4.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:14 | linux | before 7.2.11-1 | 7.2.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98983Oct 23, 2026 · unshare: don't drop active namespace references that were never taken0Monitor
- ← EarlierCVE-2026-98984Oct 23, 2026 · dcache: don't put a mountpoint on a dentry that's being removed0Monitor
- Later →CVE-2026-98986Oct 23, 2026 · namespace: remove the fsnotify marks of a mount namespace in process context0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3184a2fda996af8fcd6def36020ec023c6279015 | Vendor (CNA) |
| Linux Linux | 3c2441e21c3df867e4131e0ff784ecdb3a7a55f8 | Vendor (CNA) |
| Linux Linux | 3dad2330c89343ba083cf7868779083fd5fbe0fe | Vendor (CNA) |
| Linux Linux | 4.1 | Vendor (CNA) |
| Linux Linux | 43fd2e2ec66e6db26b6ea3e9e7a4c1018455e1b0 | Vendor (CNA) |
| Linux Linux | 5b5f8d0895cfa9f781ce107225d578897203444f | Vendor (CNA) |
| Linux Linux | 6b7c001eb5857fa09041f47673666060a2e5fc1c | Vendor (CNA) |
| Linux Linux | a56d4f8f8f4c5d9ac339d5c03a9d90eecd3697fc | Vendor (CNA) |
| Linux Linux | e3aba6900483f64e6c9eb328150dd633b7d36c1c | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 7.2.11-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 1, 2026+9 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1390 · Oct 26, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.