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-98979namespace: refuse an automount below a mount that is in no namespace

Description

In the Linux kernel, the following vulnerability has been resolved: namespace: refuse an automount below a mount that is in no namespace It's possible to add autmounts even when the parent mount isn't in the mount namespace of the caller. The only requirement we have is that the parent mount namespace must not be NULL, i.e., unmounted. Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes that trivially true. So that passes the test and attach_recursive_mnt() accepts that as a mount point and funny enough, count_mounts() dereferences MNT_NS_INTERNAL. The problem is it is an error pointer... So we can reach this in userspace via fanotify. A filesystem mark on the lower filesystem of an overlay reports paths on the layer clone and reading the event hands out a descriptor on it. For example with debugfs as the lower layer it goes kaboom: openat(evfd, "tracing", O_DIRECTORY) Oops: general protection fault KASAN: null-ptr-deref in range [0x1d0-0x1d7] RIP: 0010:count_mounts+0x35/0x200 attach_recursive_mnt finish_automount And since that sleeping beauty happens under namespace_sem held for writing every mount operation on the system blocks from then on. Congrats. Use is_mounted() instead which rejects unmounted and internal mounts alike. The open fails with EINVAL just as it did before clone_private_mount() used MNT_NS_INTERNAL.

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.21% · top 89% of all CVEs (19 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 df820f8de4e481222b17f9bcee7b909ae8167529 – < d8c7f74adf5de78035d41aa33c8f71e12b3ca430
    • affected df820f8de4e481222b17f9bcee7b909ae8167529 – < c88546071d30417ab9e55821c83f4dc7756cff6f
    • affected df820f8de4e481222b17f9bcee7b909ae8167529 – < c98e74d73a3356ab00fc6bb9dec3c77da1ec1ce4
    • affected df820f8de4e481222b17f9bcee7b909ae8167529 – < 95fb7c259b86f5521f04973040ad492f2bef6f82
    • affected df820f8de4e481222b17f9bcee7b909ae8167529 – < 35f2013f83ef16f9f0331c4c3a8e8d161580d574
    • affected df820f8de4e481222b17f9bcee7b909ae8167529 – < 494c57572d2d5bc2839553ed41aabe92ed0f587c
    • affected df820f8de4e481222b17f9bcee7b909ae8167529 – < 776e20e4fdc23c23687b511ffdc80047878049d3
    • affected df820f8de4e481222b17f9bcee7b909ae8167529 – < ba985ce08471c555af2a2fbe217c1bc2e72a6d8c
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • 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-98979 badge
[![CVE-2026-98979](https://cveledger.app/badge/CVE-2026-98979.svg)](https://cveledger.app/cve/CVE-2026-98979)

Record last updated .