FKIE_CVE-2026-98990
Vulnerability from fkie_nvd - Published: 2026-10-23 13:17 - Updated: 2026-10-23 13:17
Severity
Summary
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/namespace.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "f6394281834492c6516a405a348b545ae698a331",
"status": "affected",
"version": "1064f874abc0d05eeed8993815f584d847b72486",
"versionType": "git"
},
{
"lessThan": "6e4012e571867868b545c91ca9d6095fdb709907",
"status": "affected",
"version": "1064f874abc0d05eeed8993815f584d847b72486",
"versionType": "git"
},
{
"lessThan": "d73f04e92c1aab78d96ac6cadb234c8a3a373d22",
"status": "affected",
"version": "1064f874abc0d05eeed8993815f584d847b72486",
"versionType": "git"
},
{
"lessThan": "18902a23ef36f83d32bafc58ae2484e6bb4bb8ef",
"status": "affected",
"version": "1064f874abc0d05eeed8993815f584d847b72486",
"versionType": "git"
},
{
"lessThan": "32bf92416614a1e3ff3524fc6b780259c7aad3ef",
"status": "affected",
"version": "1064f874abc0d05eeed8993815f584d847b72486",
"versionType": "git"
},
{
"status": "affected",
"version": "5e6ef5ef6eaf690faad3a7c6c665ebf45d7b6ccf",
"versionType": "git"
},
{
"status": "affected",
"version": "839d42687dfce0ed0ea2c6bd8d707cc0e276fbe7",
"versionType": "git"
},
{
"status": "affected",
"version": "808e83e5add13152bd4a88346487de68395c136b",
"versionType": "git"
},
{
"status": "affected",
"version": "6de9d08a9718ee9c12ba6343c50141c2d633e3dc",
"versionType": "git"
},
{
"lessThan": "4.2",
"status": "affected",
"version": "4.1.40",
"versionType": "semver"
},
{
"lessThan": "4.5",
"status": "affected",
"version": "4.4.54",
"versionType": "semver"
},
{
"lessThan": "4.10",
"status": "affected",
"version": "4.9.15",
"versionType": "semver"
},
{
"lessThan": "4.11",
"status": "affected",
"version": "4.10.3",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/namespace.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.11"
},
{
"lessThan": "4.11",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.160",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.113",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.57",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.11",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: check a submount for references right before unmounting it\n\nshrink_submounts() and mark_mounts_for_expiry() first collect all the\nmounts they are allowed to unmount and then unmount them.\n\nWhether a mount is busy is decided by propagate_mount_busy() on the\ntree. But unmounting the first mount changes the tree that the second\none propagates into. propagate_umount()\nmoves a surviving overmount off a copy it unmounts and mounts it where\nthe copy was mounted. If that\u0027s where the propagated copy of the second\nvictim is looked up the overmount becomes a candidate of the second\numount_tree(). It\u0027s childless and so trim_one() commits it without\nlooking at its reference count.\n\nSo a synchronous umount pulls out a busy mount that is in use somewhere\nelse and marks it MNT_SYNC_UMOUNT while it has users:\n\n umount2(/tmp/plshrink/p1, 0) = 0 errno 0\n cwd is (unreachable)\n\nThe same two umounts requested one after the other fail with EBUSY.\nThis needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of\nNFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts\ninherit the flag.\n\nCheck each mount right before it is unmounted under the same hold of\nnamespace_sem and mount_lock as the umount itself. Make sure that the\nalgorithm stays linear."
}
],
"id": "CVE-2026-98990",
"lastModified": "2026-10-23T13:17:20.980",
"metrics": {},
"published": "2026-10-23T13:17:20.980",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/18902a23ef36f83d32bafc58ae2484e6bb4bb8ef"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/32bf92416614a1e3ff3524fc6b780259c7aad3ef"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/6e4012e571867868b545c91ca9d6095fdb709907"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d73f04e92c1aab78d96ac6cadb234c8a3a373d22"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f6394281834492c6516a405a348b545ae698a331"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.