CVE-2026-98992

published 23 Oct 2026 · updated 30 Oct 2026

namespace: don't copy an unmounted mount tree

4.4MediumCVSS 4.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 07c6a8f004bcc58b4ccf993e6efa7b9b8b4a1b8b, Kernel 31cf157298271392ab5fb0805b28d37c8d7a8057, Kernel 7e037b1fd339d865737c8accd29abcf40130a5a0 and 5 more.

In the Linux kernel, the following vulnerability has been resolved: namespace: don't copy an unmounted mount tree may_copy_tree() accepts a mount whose root is an nsfs or pidfs file before it checks whether that mount is mounted. This exception exists for nsfs and pidfs mounts. They are part of no mount namespace so neither check_mnt() nor is_mounted() would let them through and bind-mounting a nsfsfd or a pidfd wouldn't work. Problem is that exception also admits a bind mount of such a file when it was lazily unmounted and is only kept alive by a file descriptor: mount --bind /proc/self/ns/net /tmp/x exec 3< /tmp/x umount -l /tmp/x mount --rbind /proc/self/fd/3 /tmp/y With MS_REC or AT_RECURSIVE copy_tree() doesn't stop at the unmounted mount. It copies every mount that stayed attached to it as well. So if you have a bunch of overmounts over the nsfsfd or the pidfd the whole unmounted stack is copied. That's a bug. So refuse to walk an unmounted tree. Copying its root alone stays possible. So a bind mount of a namespace that is gone can still be recreated from a file descriptor on the old one. The file descriptor pins that mount and its root and __has_locked_children() only reads the direct children which don't leave the parent's list without namespace_sem. The internal mounts carry MNT_NS_INTERNAL instead of NULL and are still walked. Copying an unmounted tree recursively fails with EINVAL.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.19, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <07c6a8f004bcc58b4ccf993e6efa7b9b8b4a1b8b, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <31cf157298271392ab5fb0805b28d37c8d7a8057, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <7e037b1fd339d865737c8accd29abcf40130a5a0, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <86a2d56b1960720bf1844441c0890621e9db2f25, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <8bacbf6be959973b28b691713a872c12eae69eec, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <8d3527457e183cedee3003c2897314da49488311, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <94d05b62dc7aea236db20166e79ee002e466393a, >=e149ed2b805fefdccf7ccdfc19eca22fdd4514ac <b47b40c4f058418f9707454543179df240796aad07c6a8f004bcc58b4ccf993e6efa7b9b8b4a1b8b, 31cf157298271392ab5fb0805b28d37c8d7a8057, 7e037b1fd339d865737c8accd29abcf40130a5a0, 86a2d56b1960720bf1844441c0890621e9db2f25, 8bacbf6be959973b28b691713a872c12eae69eec, 8d3527457e183cedee3003c2897314da49488311, 94d05b62dc7aea236db20166e79ee002e466393a, b47b40c4f058418f9707454543179df240796aad

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98992 severity on Zeptric[![CVE-2026-98992](https://zeptric.io/badge/cve/CVE-2026-98992.svg)](https://zeptric.io/cve/CVE-2026-98992)