Process isolation via shared fs_struct namespace copy
Published May 8, 2026 · Updated May 8, 2026
Resource-state corruption in the Linux Kernel allows local users to leave a process rooted on detached mounts through unshare(2). When CLONE_NEWNS is requested for an unshared fs_struct, unshare_fs() passes current->fs to copy_mnt_ns() instead of allocating a private copy. If later CLONE_NEWCGROUP processing fails, cleanup dissolves the new mount tree while pwd and root still pin its detached mounts, isolating the calling process.
Summary
What happened
Resource-state corruption in the Linux Kernel allows local users to leave a process rooted on detached mounts through unshare(2). When CLONE_NEWNS is requested for an unshared fs_struct, unshare_fs() passes current->fs to copy_mnt_ns() instead of allocating a private copy. If later CLONE_NEWCGROUP processing fails, cleanup dissolves the new mount tree while pwd and root still pin its detached mounts, isolating the calling process.
The record
- CVE
- CVE-2026-43472
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <42e21e74061b0ebbd859839f81acf10efad02a27
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6c4b2243cb6c0755159bd567130d5e12e7b10d9f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <845bf3c6963a52096d0d3866e4a92db77a0c03d8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aa9ebc084505fb26dd90f4d7a249045aad152043
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <af8f4be3b68ac8caa41c8e5ead0eeaf5e85e42d0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d0d99f60538ddb4a62ccaac2168d8f448965f083
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d3ffc8f13034af895531a02c30b1fe3a34b46432
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d7963d6997fea86a6def242ac36198b86655f912
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo