CVE-2026-98987 (GCVE-0-2026-98987)
Vulnerability from cvelistv5 – Published: 2026-10-23 12:20 – Updated: 2026-10-23 12:20
VLAI
EPSS
VEX
Title
namespace: look at the topmost mount for a mount namespace file
Summary
In the Linux kernel, the following vulnerability has been resolved:
namespace: look at the topmost mount for a mount namespace file
attach_recursive_mnt() preallocates a mountpoint for the root of the
topmost mount of the source so that a mount that already sits at the
destination can be put on top of the source or on top of one of its
propagated copies.
The copies are made without CL_COPY_MNT_NS_FILE so their chain of
overmounts is shorter than the source's. It ends below the first bind
mount of a mount namespace file. So while the loop walks up the chain of
the source it remembers the mountpoint of that mount in "shorter" and
the existing mount is put there for the copies.
But the loop ends at the topmost mount without ever looking at it. If
the topmost mount is the only mount namespace file in the chain
"shorter" stays NULL and mnt_change_mountpoint() attaches the existing
mount of the copy below the root of the mount namespace file. That's a
dentry of nsfs. No path walk in the copy's mount namespace ever gets
there. The mount is gone until its parent goes and the copy that took
its place can't be unmounted synchronously because it has a child:
S bind mount of a file
N bind mount of a mount namespace file on top of S
A shared mount, B a slave of A, Q mounted on B/file
move_mount(S, A/file)
cat B/file -> the content of S instead of Q
umount B/file -> EBUSY
Look at every mount of the chain including the topmost one.
Severity
No CVSS data available.
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
96f5d2e051653f2cfe9137c5d3c7794c358ffb03 , < b9c40553f6ceba50042281eef6f701e5fb719726
(git)
Affected: 96f5d2e051653f2cfe9137c5d3c7794c358ffb03 , < 87ecd4c6da146363384a603bd9e90c90e7275536 (git) Affected: 96f5d2e051653f2cfe9137c5d3c7794c358ffb03 , < 8714b44adac7b10506e1db3ef1710689751f0f10 (git) |
guessed | |
| Linux | Linux |
Affected:
6.17
Unaffected: 0 , < 6.17 (semver) Unaffected: 6.18.57 , ≤ 6.18.* (semver) Unaffected: 7.2.11 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"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": "b9c40553f6ceba50042281eef6f701e5fb719726",
"status": "affected",
"version": "96f5d2e051653f2cfe9137c5d3c7794c358ffb03",
"versionType": "git"
},
{
"lessThan": "87ecd4c6da146363384a603bd9e90c90e7275536",
"status": "affected",
"version": "96f5d2e051653f2cfe9137c5d3c7794c358ffb03",
"versionType": "git"
},
{
"lessThan": "8714b44adac7b10506e1db3ef1710689751f0f10",
"status": "affected",
"version": "96f5d2e051653f2cfe9137c5d3c7794c358ffb03",
"versionType": "git"
}
]
},
{
"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": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"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"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.57",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.11",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "6.17",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: look at the topmost mount for a mount namespace file\n\nattach_recursive_mnt() preallocates a mountpoint for the root of the\ntopmost mount of the source so that a mount that already sits at the\ndestination can be put on top of the source or on top of one of its\npropagated copies.\n\nThe copies are made without CL_COPY_MNT_NS_FILE so their chain of\novermounts is shorter than the source\u0027s. It ends below the first bind\nmount of a mount namespace file. So while the loop walks up the chain of\nthe source it remembers the mountpoint of that mount in \"shorter\" and\nthe existing mount is put there for the copies.\n\nBut the loop ends at the topmost mount without ever looking at it. If\nthe topmost mount is the only mount namespace file in the chain\n\"shorter\" stays NULL and mnt_change_mountpoint() attaches the existing\nmount of the copy below the root of the mount namespace file. That\u0027s a\ndentry of nsfs. No path walk in the copy\u0027s mount namespace ever gets\nthere. The mount is gone until its parent goes and the copy that took\nits place can\u0027t be unmounted synchronously because it has a child:\n\n S bind mount of a file\n N bind mount of a mount namespace file on top of S\n A shared mount, B a slave of A, Q mounted on B/file\n\n move_mount(S, A/file)\n cat B/file -\u003e the content of S instead of Q\n umount B/file -\u003e EBUSY\n\nLook at every mount of the chain including the topmost one."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-23T12:20:06.180Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/b9c40553f6ceba50042281eef6f701e5fb719726"
},
{
"url": "https://git.kernel.org/stable/c/87ecd4c6da146363384a603bd9e90c90e7275536"
},
{
"url": "https://git.kernel.org/stable/c/8714b44adac7b10506e1db3ef1710689751f0f10"
}
],
"title": "namespace: look at the topmost mount for a mount namespace file",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98987",
"datePublished": "2026-10-23T12:20:06.180Z",
"dateReserved": "2026-09-25T10:25:14.384Z",
"dateUpdated": "2026-10-23T12:20:06.180Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"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": "b9c40553f6ceba50042281eef6f701e5fb719726",
"status": "affected",
"version": "96f5d2e051653f2cfe9137c5d3c7794c358ffb03",
"versionType": "git"
},
{
"lessThan": "87ecd4c6da146363384a603bd9e90c90e7275536",
"status": "affected",
"version": "96f5d2e051653f2cfe9137c5d3c7794c358ffb03",
"versionType": "git"
},
{
"lessThan": "8714b44adac7b10506e1db3ef1710689751f0f10",
"status": "affected",
"version": "96f5d2e051653f2cfe9137c5d3c7794c358ffb03",
"versionType": "git"
}
]
},
{
"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": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"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: look at the topmost mount for a mount namespace file\n\nattach_recursive_mnt() preallocates a mountpoint for the root of the\ntopmost mount of the source so that a mount that already sits at the\ndestination can be put on top of the source or on top of one of its\npropagated copies.\n\nThe copies are made without CL_COPY_MNT_NS_FILE so their chain of\novermounts is shorter than the source\u0027s. It ends below the first bind\nmount of a mount namespace file. So while the loop walks up the chain of\nthe source it remembers the mountpoint of that mount in \"shorter\" and\nthe existing mount is put there for the copies.\n\nBut the loop ends at the topmost mount without ever looking at it. If\nthe topmost mount is the only mount namespace file in the chain\n\"shorter\" stays NULL and mnt_change_mountpoint() attaches the existing\nmount of the copy below the root of the mount namespace file. That\u0027s a\ndentry of nsfs. No path walk in the copy\u0027s mount namespace ever gets\nthere. The mount is gone until its parent goes and the copy that took\nits place can\u0027t be unmounted synchronously because it has a child:\n\n S bind mount of a file\n N bind mount of a mount namespace file on top of S\n A shared mount, B a slave of A, Q mounted on B/file\n\n move_mount(S, A/file)\n cat B/file -\u003e the content of S instead of Q\n umount B/file -\u003e EBUSY\n\nLook at every mount of the chain including the topmost one."
}
],
"id": "CVE-2026-98987",
"lastModified": "2026-10-23T13:17:20.643",
"metrics": {},
"published": "2026-10-23T13:17:20.643",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8714b44adac7b10506e1db3ef1710689751f0f10"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/87ecd4c6da146363384a603bd9e90c90e7275536"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b9c40553f6ceba50042281eef6f701e5fb719726"
}
],
"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.