Mount restriction bypass via wrong-namespace automount locking
Published Oct 23, 2026 · Updated Oct 23, 2026
Mount restriction bypass in Linux automount handling allows local users to clear security flags through cross-namespace propagation. In fs/namespace.c, attach_recursive_mnt() selects the triggering task's user namespace instead of the destination mount namespace, locking the host automount rather than the child's copy. Exploitation requires namespace creation and a directory descriptor into a shared host mount with an inactive automount; the child can remove nosuid, nodev, and noexec restrictions while host flag changes fail.
Summary
What happened
Mount restriction bypass in Linux automount handling allows local users to clear security flags through cross-namespace propagation. In fs/namespace.c, attach_recursive_mnt() selects the triggering task's user namespace instead of the destination mount namespace, locking the host automount rather than the child's copy. Exploitation requires namespace creation and a directory descriptor into a shared host mount with an inactive automount; the child can remove nosuid, nodev, and noexec restrictions while host flag changes fail.
The record
- CVE
- CVE-2026-98977
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 <33aadc7c72055fca93cb5a3691d836ebf8b31c9b
- Affected versionversion=132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 <5e8f3ac8fa3d411b422ad32b9168c46a4824cc79
- Affected versionversion=132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 <6ab37fae14196ba2262b152a7d9222c50356d278
- Affected versionversion=132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 <b3ccde78f1608836e62320428abc0e8aa9cf2329
- Affected versionversion=132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 <e01c79761c7b3373e80094c5eadb21cb864fa8bc
- Affected versionversion=3.8.6 <3.9
- Affected versionversion=3.9
- Affected versionversion=9c773201d61272db49f8f33a83a3cb2a3fe4b14f
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Upstream cross-namespace automount reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us