CVE-2026-98977

namespace: handle mount locking for automounts correctly

Description

In the Linux kernel, the following vulnerability has been resolved: namespace: handle mount locking for automounts correctly If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories. The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup. Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore. Here's the reproducer: - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs mount that receives propagation from it - child process stats "tracing/." through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount: host, on its own automount: MS_REMOUNT|MS_BIND = EPERM child, on the copy in its namespace: MS_REMOUNT|MS_BIND = 0 So the lock landed on the host's mount instead of the child's copy. Congrats. So we need to compare with the owner of the namespace the mount actually gets mounted on. For all regular cases that is the caller's mount namespace and so nothing changes. Detached trees in anonymous mount namespaces by be handed over via SCM_RIGHTS or inherited in other ways on purpose so the attaching task's mount namespace is authoritative, not the creator of the detached tree.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.22% likely to be exploited in the next 30 days, higher than 12.71% 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
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding f9b488641cfa63f9b41321530c543688b2e34f03 (affected)
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding 91676705756af6a59a515087b8b854c8a28d12eb (affected)
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding 587d25c4b13d49c8fd05df2f71240f73bb2a058c (affected)
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding 5e8f3ac8fa3d411b422ad32b9168c46a4824cc79 (affected)
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding b3ccde78f1608836e62320428abc0e8aa9cf2329 (affected)
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding e01c79761c7b3373e80094c5eadb21cb864fa8bc (affected)
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding 6ab37fae14196ba2262b152a7d9222c50356d278 (affected)
  • 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 up to but excluding 33aadc7c72055fca93cb5a3691d836ebf8b31c9b (affected)
  • 9c773201d61272db49f8f33a83a3cb2a3fe4b14f (affected)
  • 3.8.6 up to but excluding 3.9 (affected)
LinuxLinux
  • Default status: affected
  • 3.9 (affected)
  • 0 up to but excluding 3.9 (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.114 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