Linux: namespace: check the mounts before reading their parents in pivot_root()
What fixes it
- 3c2441e21c3df867e4131e0ff784ecdb3a7a55f8LinuxCVE List
- 3dad2330c89343ba083cf7868779083fd5fbe0feLinuxCVE List
- 6b7c001eb5857fa09041f47673666060a2e5fc1cLinuxCVE List
- 4.1LinuxCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
In the Linux kernel, the following vulnerability has been resolved:
namespace: check the mounts before reading their parents in pivot_root()
path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace.
But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards:
pivot_root() close(fd), last ref on the parent ------------ --------------------------------- ex_parent = new_mnt->mnt_parent mntput_no_expire_slowpath() __umount_mnt(new_mnt) cleanup_mnt() call_rcu() IS_MNT_SHARED(ex_parent)
BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840 Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157 path_pivot_root+0xf1a/0x1840 __x64_sys_pivot_root+0x165/0x190
The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 ("statmount: read the parent of an unmounted mount under mount_lock") fixed for statmount().
Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.
Text from CVE List
Affected versions 14
- Linuxaffected: e0c9c0afd2fc958ffa34b697972721d81df8a56f before a56d4f8f8f4c5d9ac339d5c03a9d90eecd3697fcCVE List
- Linuxaffected: e0c9c0afd2fc958ffa34b697972721d81df8a56f before 3c2441e21c3df867e4131e0ff784ecdb3a7a55f8CVE List
- Linuxaffected: e0c9c0afd2fc958ffa34b697972721d81df8a56f before e3aba6900483f64e6c9eb328150dd633b7d36c1cCVE List
- Linuxaffected: e0c9c0afd2fc958ffa34b697972721d81df8a56f before 3dad2330c89343ba083cf7868779083fd5fbe0feCVE List
- Linuxaffected: e0c9c0afd2fc958ffa34b697972721d81df8a56f before 6b7c001eb5857fa09041f47673666060a2e5fc1cCVE List
- Linuxaffected: 84b78514033ff22c443473214ab6d0508394cf7aCVE List
- Linuxaffected: 4.0.2 before 4.1CVE List
- Linuxaffected: 4.1CVE List
- Linuxunaffected: all versions before 4.1CVE List
- Linuxunaffected: 6.6.160 through 6.6.*CVE List
- Linuxunaffected: 6.12.114 through 6.12.*CVE List
- Linuxunaffected: 6.18.57 through 6.18.*CVE List
- Linuxunaffected: 7.2.11 through 7.2.*CVE List
- Linuxunaffected: 7.3CVE List
References 5
- git.kernel.org/stable/c/a56d4f8f8f4c5d9ac339d5c03a9d90eecd3697fcReferencevia CVE List
- git.kernel.org/stable/c/3c2441e21c3df867e4131e0ff784ecdb3a7a55f8Referencevia CVE List
- git.kernel.org/stable/c/e3aba6900483f64e6c9eb328150dd633b7d36c1cReferencevia CVE List
- git.kernel.org/stable/c/3dad2330c89343ba083cf7868779083fd5fbe0feReferencevia CVE List
- git.kernel.org/stable/c/6b7c001eb5857fa09041f47673666060a2e5fc1cReferencevia CVE List