namespace: look at the topmost mount for a mount namespace file
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.57, 7.2.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: namespace: look at the topmost mount for a mount namespace file attach_recursive_mnt() preallocates a mountpoint for the root of the topmost mount of the source so that a mount that already sits at the destination can be put on top of the source or on top of one of its propagated copies. The copies are made without CL_COPY_MNT_NS_FILE so their chain of overmounts is shorter than the source's. It ends below the first bind mount of a mount namespace file. So while the loop walks up the chain of the source it remembers the mountpoint of that mount in "shorter" and the existing mount is put there for the copies. But the loop ends at the topmost mount without ever looking at it. If the topmost mount is the only mount namespace file in the chain "shorter" stays NULL and mnt_change_mountpoint() attaches the existing mount of the copy below the root of the mount namespace file. That's a dentry of nsfs. No path walk in the copy's mount namespace ever gets there. The mount is gone until its parent goes and the copy that took its place can't be unmounted synchronously because it has a child: S bind mount of a file N bind mount of a mount namespace file on top of S A shared mount, B a slave of A, Q mounted on B/file move_mount(S, A/file) cat B/file -> the content of S instead of Q umount B/file -> EBUSY Look at every mount of the chain including the topmost one.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From 96f5d2e051653f2cfe9137c5d3c7794c358ffb03 · fixed in b9c40553f6ceba50042281eef6f701e5fb719726; From 96f5d2e051653f2cfe9137c5d3c7794c358ffb03 · fixed in 87ecd4c6da146363384a603bd9e90c90e7275536; From 96f5d2e051653f2cfe9137c5d3c7794c358ffb03 · fixed in 8714b44adac7b10506e1db3ef1710689751f0f10
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11