CVE-2026-98978

published 23 Oct 2026 · updated 12 Nov 2026

namespace: never expire a locked mount

8.4HighCVSS 8.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f78ddcc872248c7aa1d7e904928441a0be4c6d5d, Kernel 6b8dc3713a76346d212abab46cbfc8d7070f534c, Kernel 6c8013ea84fcc51cf26aa870b61b5388c7196ed5 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: namespace: never expire a locked mount Locked mounts are special. They protect the underlying files and directories from being revealed. do_umount() refuses to unmount locked mounts but shrink_submounts() doesn't. A shrinkable mount can become locked once the owner of a user namespace puts it beneath a locked mount with MOVE_MOUNT_BENEATH. The locked property now moves to the mount at the bottom making it possible to unmount the top mount. So umount() of an unlocked ancestor now expires the bottom mount first and the covered directory is revealed: move_mount(c -> x/hidden, MOVE_MOUNT_BENEATH) = 0 the cover after the lock moved: umount2(x/hidden) = 0 the holder of the lock: umount2(x/hidden) = EINVAL the root of the copy, busy: umount2(x) = EBUSY reads x/hidden/secret: "covered-by-root" So leave a locked mount alone as it dies together with its parent. A plain umount() of an unlocked mount with a locked one below it is EBUSY from now on. It's the same for any other locked child. A lazy umount still takes the whole tree. mark_mounts_for_expiry() never sees a locked mount. lock_mnt_tree() leaves a mount on an expiry list alone and nothing else puts a locked one on such a list. Add an assert for this.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 <f78ddcc872248c7aa1d7e904928441a0be4c6d5d, >=5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 <6b8dc3713a76346d212abab46cbfc8d7070f534c, >=5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 <6c8013ea84fcc51cf26aa870b61b5388c7196ed5, >=5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 <d23265a12e4991ce7aedce670c0b6b598cadb644, =3.12f78ddcc872248c7aa1d7e904928441a0be4c6d5d, 6b8dc3713a76346d212abab46cbfc8d7070f534c, 6c8013ea84fcc51cf26aa870b61b5388c7196ed5, d23265a12e4991ce7aedce670c0b6b598cadb644
linux-kernel: Kernel>=6.13.0 <6.18.57, >=6.19.0 <7.2.11, >=3.12.0 <6.12.1176.18.57, 7.2.11, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98978 severity on Zeptric[![CVE-2026-98978](https://zeptric.io/badge/cve/CVE-2026-98978.svg)](https://zeptric.io/cve/CVE-2026-98978)