CVE-2026-98990

namespace: check a submount for references right before unmounting it

Description

In the Linux kernel, the following vulnerability has been resolved: namespace: check a submount for references right before unmounting it shrink_submounts() and mark_mounts_for_expiry() first collect all the mounts they are allowed to unmount and then unmount them. Whether a mount is busy is decided by propagate_mount_busy() on the tree. But unmounting the first mount changes the tree that the second one propagates into. propagate_umount() moves a surviving overmount off a copy it unmounts and mounts it where the copy was mounted. If that's where the propagated copy of the second victim is looked up the overmount becomes a candidate of the second umount_tree(). It's childless and so trim_one() commits it without looking at its reference count. So a synchronous umount pulls out a busy mount that is in use somewhere else and marks it MNT_SYNC_UMOUNT while it has users: umount2(/tmp/plshrink/p1, 0) = 0 errno 0 cwd is (unreachable) The same two umounts requested one after the other fail with EBUSY. This needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of NFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts inherit the flag. Check each mount right before it is unmounted under the same hold of namespace_sem and mount_lock as the umount itself. Make sure that the algorithm stays linear.

Key facts

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

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
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding cda0c4e502a0f74a191471ce100fb061e5ab35d6 (affected)
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding 3f55f71291e4332983cd63b288d1f2be3c9c08fc (affected)
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding 361f59e7f3f9a219fb5567bf9abc8482a154a399 (affected)
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding f6394281834492c6516a405a348b545ae698a331 (affected)
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding 6e4012e571867868b545c91ca9d6095fdb709907 (affected)
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding d73f04e92c1aab78d96ac6cadb234c8a3a373d22 (affected)
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding 18902a23ef36f83d32bafc58ae2484e6bb4bb8ef (affected)
  • 1064f874abc0d05eeed8993815f584d847b72486 up to but excluding 32bf92416614a1e3ff3524fc6b780259c7aad3ef (affected)
  • 5e6ef5ef6eaf690faad3a7c6c665ebf45d7b6ccf (affected)
  • 839d42687dfce0ed0ea2c6bd8d707cc0e276fbe7 (affected)
  • 808e83e5add13152bd4a88346487de68395c136b (affected)
  • 6de9d08a9718ee9c12ba6343c50141c2d633e3dc (affected)
  • 4.1.40 up to but excluding 4.2 (affected)
  • 4.4.54 up to but excluding 4.5 (affected)
  • 4.9.15 up to but excluding 4.10 (affected)
  • 4.10.3 up to but excluding 4.11 (affected)
LinuxLinux
  • Default status: affected
  • 4.11 (affected)
  • 0 up to but excluding 4.11 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 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