CVE-2026-98977 (GCVE-0-2026-98977)
Vulnerability from cvelistv5 – Published: 2026-10-23 12:19 – Updated: 2026-10-23 12:19
VLAI
EPSS
VEX
Title
namespace: handle mount locking for automounts correctly
Summary
In the Linux kernel, the following vulnerability has been resolved:
namespace: handle mount locking for automounts correctly
If mounts are propagated across user namespaces, attach_recursive_mnt()
locks every copy of the source mount to protect overmounts from
vanishing and revealing the underlying files or directories.
The user namespace is taken from the caller's mount namespaces since
this is where the mounts end up. Except, that's not always true.
Automounts may legitimately get popped in by tasks located in a
different mount and user namespace during path lookup.
Then check doesn't make sense at that point. The copy in the namespace
of the parent - which may be the host's - is now locked and the host
cannot change the flags of its own mounts anymore.
Here's the reproducer:
- host has debugfs mounted nosuid,nodev,noexec and shared
- tracefs automount below it is not yet active
- hand a child process a directory descriptor on that mount
- child process enters auser and mount namespace
- child process' namespace now holds a locked copy of the host's debugfs
mount that receives propagation from it
- child process stats "tracing/." through the descriptor
- lookup runs on the host's mount so the automount lands below the host's mount
- propagation puts a copy below the child's copy
- both try to clear the flags on the mount they got, with a bind remount:
host, on its own automount: MS_REMOUNT|MS_BIND = EPERM
child, on the copy in its namespace: MS_REMOUNT|MS_BIND = 0
So the lock landed on the host's mount instead of the child's copy.
Congrats. So we need to compare with the owner of the namespace the
mount actually gets mounted on. For all regular cases that is the
caller's mount namespace and so nothing changes.
Detached trees in anonymous mount namespaces by be handed over via
SCM_RIGHTS or inherited in other ways on purpose so the attaching task's
mount namespace is authoritative, not the creator of the detached tree.
Severity
No CVSS data available.
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 , < 5e8f3ac8fa3d411b422ad32b9168c46a4824cc79
(git)
Affected: 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 , < b3ccde78f1608836e62320428abc0e8aa9cf2329 (git) Affected: 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 , < e01c79761c7b3373e80094c5eadb21cb864fa8bc (git) Affected: 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 , < 6ab37fae14196ba2262b152a7d9222c50356d278 (git) Affected: 132c94e31b8bca8ea921f9f96a57d684fa4ae0a9 , < 33aadc7c72055fca93cb5a3691d836ebf8b31c9b (git) Affected: 9c773201d61272db49f8f33a83a3cb2a3fe4b14f (git) Affected: 3.8.6 , < 3.9 (semver) |
guessed | |
| Linux | Linux |
Affected:
3.9
Unaffected: 0 , < 3.9 (semver) Unaffected: 6.6.160 , ≤ 6.6.* (semver) Unaffected: 6.12.114 , ≤ 6.12.* (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": "5e8f3ac8fa3d411b422ad32b9168c46a4824cc79",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "b3ccde78f1608836e62320428abc0e8aa9cf2329",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "e01c79761c7b3373e80094c5eadb21cb864fa8bc",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "6ab37fae14196ba2262b152a7d9222c50356d278",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "33aadc7c72055fca93cb5a3691d836ebf8b31c9b",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"status": "affected",
"version": "9c773201d61272db49f8f33a83a3cb2a3fe4b14f",
"versionType": "git"
},
{
"lessThan": "3.9",
"status": "affected",
"version": "3.8.6",
"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": "3.9"
},
{
"lessThan": "3.9",
"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.114",
"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.6.160",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.114",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.57",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.11",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "3.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "3.8.6",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: handle mount locking for automounts correctly\n\nIf mounts are propagated across user namespaces, attach_recursive_mnt()\nlocks every copy of the source mount to protect overmounts from\nvanishing and revealing the underlying files or directories.\n\nThe user namespace is taken from the caller\u0027s mount namespaces since\nthis is where the mounts end up. Except, that\u0027s not always true.\nAutomounts may legitimately get popped in by tasks located in a\ndifferent mount and user namespace during path lookup.\n\nThen check doesn\u0027t make sense at that point. The copy in the namespace\nof the parent - which may be the host\u0027s - is now locked and the host\ncannot change the flags of its own mounts anymore.\n\nHere\u0027s the reproducer:\n\n- host has debugfs mounted nosuid,nodev,noexec and shared\n- tracefs automount below it is not yet active\n- hand a child process a directory descriptor on that mount\n- child process enters auser and mount namespace\n- child process\u0027 namespace now holds a locked copy of the host\u0027s debugfs\n mount that receives propagation from it\n- child process stats \"tracing/.\" through the descriptor\n- lookup runs on the host\u0027s mount so the automount lands below the host\u0027s mount\n- propagation puts a copy below the child\u0027s copy\n- both try to clear the flags on the mount they got, with a bind remount:\n\n host, on its own automount: MS_REMOUNT|MS_BIND = EPERM\n child, on the copy in its namespace: MS_REMOUNT|MS_BIND = 0\n\nSo the lock landed on the host\u0027s mount instead of the child\u0027s copy.\nCongrats. So we need to compare with the owner of the namespace the\nmount actually gets mounted on. For all regular cases that is the\ncaller\u0027s mount namespace and so nothing changes.\n\nDetached trees in anonymous mount namespaces by be handed over via\nSCM_RIGHTS or inherited in other ways on purpose so the attaching task\u0027s\nmount namespace is authoritative, not the creator of the detached tree."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-23T12:19:50.475Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/5e8f3ac8fa3d411b422ad32b9168c46a4824cc79"
},
{
"url": "https://git.kernel.org/stable/c/b3ccde78f1608836e62320428abc0e8aa9cf2329"
},
{
"url": "https://git.kernel.org/stable/c/e01c79761c7b3373e80094c5eadb21cb864fa8bc"
},
{
"url": "https://git.kernel.org/stable/c/6ab37fae14196ba2262b152a7d9222c50356d278"
},
{
"url": "https://git.kernel.org/stable/c/33aadc7c72055fca93cb5a3691d836ebf8b31c9b"
}
],
"title": "namespace: handle mount locking for automounts correctly",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98977",
"datePublished": "2026-10-23T12:19:50.475Z",
"dateReserved": "2026-09-25T10:25:14.383Z",
"dateUpdated": "2026-10-23T12:19:50.475Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-98977",
"date": "2026-10-24",
"epss": "0.00209",
"percentile": "0.10465"
},
"microsoft_vex": {
"current_release_date": "2026-10-24T01:10:38.000Z",
"cve": "CVE-2026-98977",
"id": "msrc_CVE-2026-98977",
"initial_release_date": "2026-10-24T01:10:38.000Z",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "namespace: handle mount locking for automounts correctly",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-98977.json",
"version": "1"
},
"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": "5e8f3ac8fa3d411b422ad32b9168c46a4824cc79",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "b3ccde78f1608836e62320428abc0e8aa9cf2329",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "e01c79761c7b3373e80094c5eadb21cb864fa8bc",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "6ab37fae14196ba2262b152a7d9222c50356d278",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"lessThan": "33aadc7c72055fca93cb5a3691d836ebf8b31c9b",
"status": "affected",
"version": "132c94e31b8bca8ea921f9f96a57d684fa4ae0a9",
"versionType": "git"
},
{
"status": "affected",
"version": "9c773201d61272db49f8f33a83a3cb2a3fe4b14f",
"versionType": "git"
},
{
"lessThan": "3.9",
"status": "affected",
"version": "3.8.6",
"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": "3.9"
},
{
"lessThan": "3.9",
"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.114",
"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: handle mount locking for automounts correctly\n\nIf mounts are propagated across user namespaces, attach_recursive_mnt()\nlocks every copy of the source mount to protect overmounts from\nvanishing and revealing the underlying files or directories.\n\nThe user namespace is taken from the caller\u0027s mount namespaces since\nthis is where the mounts end up. Except, that\u0027s not always true.\nAutomounts may legitimately get popped in by tasks located in a\ndifferent mount and user namespace during path lookup.\n\nThen check doesn\u0027t make sense at that point. The copy in the namespace\nof the parent - which may be the host\u0027s - is now locked and the host\ncannot change the flags of its own mounts anymore.\n\nHere\u0027s the reproducer:\n\n- host has debugfs mounted nosuid,nodev,noexec and shared\n- tracefs automount below it is not yet active\n- hand a child process a directory descriptor on that mount\n- child process enters auser and mount namespace\n- child process\u0027 namespace now holds a locked copy of the host\u0027s debugfs\n mount that receives propagation from it\n- child process stats \"tracing/.\" through the descriptor\n- lookup runs on the host\u0027s mount so the automount lands below the host\u0027s mount\n- propagation puts a copy below the child\u0027s copy\n- both try to clear the flags on the mount they got, with a bind remount:\n\n host, on its own automount: MS_REMOUNT|MS_BIND = EPERM\n child, on the copy in its namespace: MS_REMOUNT|MS_BIND = 0\n\nSo the lock landed on the host\u0027s mount instead of the child\u0027s copy.\nCongrats. So we need to compare with the owner of the namespace the\nmount actually gets mounted on. For all regular cases that is the\ncaller\u0027s mount namespace and so nothing changes.\n\nDetached trees in anonymous mount namespaces by be handed over via\nSCM_RIGHTS or inherited in other ways on purpose so the attaching task\u0027s\nmount namespace is authoritative, not the creator of the detached tree."
}
],
"id": "CVE-2026-98977",
"lastModified": "2026-10-23T13:17:19.387",
"metrics": {},
"published": "2026-10-23T13:17:19.387",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/33aadc7c72055fca93cb5a3691d836ebf8b31c9b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5e8f3ac8fa3d411b422ad32b9168c46a4824cc79"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/6ab37fae14196ba2262b152a7d9222c50356d278"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b3ccde78f1608836e62320428abc0e8aa9cf2329"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e01c79761c7b3373e80094c5eadb21cb864fa8bc"
}
],
"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.