Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98992

namespace: don't copy an unmounted mount tree

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < 94d05b62dc7aea236db20166e79ee002e466393a
    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < 07c6a8f004bcc58b4ccf993e6efa7b9b8b4a1b8b
    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < 31cf157298271392ab5fb0805b28d37c8d7a8057
    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < 86a2d56b1960720bf1844441c0890621e9db2f25
    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < 7e037b1fd339d865737c8accd29abcf40130a5a0
    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < b47b40c4f058418f9707454543179df240796aad
    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < 8d3527457e183cedee3003c2897314da49488311
    • affected e149ed2b805fefdccf7ccdfc19eca22fdd4514ac – < 8bacbf6be959973b28b691713a872c12eae69eec
  • Linux · Linux

    • affected 3.19
    • unaffected < 3.19
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98992 badge
[![CVE-2026-98992](https://cveledger.app/badge/CVE-2026-98992.svg)](https://cveledger.app/cve/CVE-2026-98992)

Record last updated .