CVE-2026-98979

namespace: 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.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.211% likely to be exploited in the next 30 days, higher than 11.375% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding d8c7f74adf5de78035d41aa33c8f71e12b3ca430 (affected)
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding c88546071d30417ab9e55821c83f4dc7756cff6f (affected)
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding c98e74d73a3356ab00fc6bb9dec3c77da1ec1ce4 (affected)
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding 95fb7c259b86f5521f04973040ad492f2bef6f82 (affected)
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding 35f2013f83ef16f9f0331c4c3a8e8d161580d574 (affected)
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding 494c57572d2d5bc2839553ed41aabe92ed0f587c (affected)
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding 776e20e4fdc23c23687b511ffdc80047878049d3 (affected)
  • df820f8de4e481222b17f9bcee7b909ae8167529 up to but excluding ba985ce08471c555af2a2fbe217c1bc2e72a6d8c (affected)
LinuxLinux
  • Default status: affected
  • 5.8 (affected)
  • 0 up to but excluding 5.8 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References