CVE-2026-98978

namespace: never expire a locked mount

  • High 8.4

Description

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.

Key facts

Published
23 Oct 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.172% likely to be exploited in the next 30 days, higher than 6.622% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.4CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 up to but excluding 6c8013ea84fcc51cf26aa870b61b5388c7196ed5 (affected)
  • 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 up to but excluding 6b8dc3713a76346d212abab46cbfc8d7070f534c (affected)
  • 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 up to but excluding d23265a12e4991ce7aedce670c0b6b598cadb644 (affected)
  • 5ff9d8a65ce80efb509ce4e8051394e9ed2cd942 up to but excluding f78ddcc872248c7aa1d7e904928441a0be4c6d5d (affected)
LinuxLinux
  • Default status: affected
  • 3.12 (affected)
  • 0 up to but excluding 3.12 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References