PoC Monitor
← All CVEs
CVE-2026-98978published 23 Oct 2026 12:19 UTCData: JSON · API

Linux

namespace: never expire a locked mount

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942, < 6c8013ea84fcc51cf26aa870b61b5388c7196ed5
  • >= 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942, < 6b8dc3713a76346d212abab46cbfc8d7070f534c
  • >= 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942, < d23265a12e4991ce7aedce670c0b6b598cadb644
  • >= 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942, < f78ddcc872248c7aa1d7e904928441a0be4c6d5d

Fixed in 6c8013ea84fcc51cf26aa870b61b5388c7196ed5, 6b8dc3713a76346d212abab46cbfc8d7070f534c, d23265a12e4991ce7aedce670c0b6b598cadb644, f78ddcc872248c7aa1d7e904928441a0be4c6d5d

Linux Linux
  • 3.12

Fixed in 0, 6.12.117, 6.18.57, 7.2.11, 7.3

Mitigation

Upgrade Linux to 6c8013ea84fcc51cf26aa870b61b5388c7196ed5 or 6b8dc3713a76346d212abab46cbfc8d7070f534c or d23265a12e4991ce7aedce670c0b6b598cadb644 or f78ddcc872248c7aa1d7e904928441a0be4c6d5d or later.

Upgrade Linux to 0 or 6.12.117 or 6.18.57 or 7.2.11 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published23 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.