CVE-2026-98979 (GCVE-0-2026-98979)
Vulnerability from cvelistv5 – Published: 2026-10-23 12:19 – Updated: 2026-10-23 12:19
VLAI
EPSS
VEX
Title
namespace: refuse an automount below a mount that is in no namespace
Summary
In the Linux kernel, the following vulnerability has been resolved:
namespace: refuse an automount below a mount that is in no namespace
It's possible to add autmounts even when the parent mount isn't in the
mount namespace of the caller. The only requirement we have is that the
parent mount namespace must not be NULL, i.e., unmounted.
Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes
that trivially true. So that passes the test and attach_recursive_mnt()
accepts that as a mount point and funny enough, count_mounts()
dereferences MNT_NS_INTERNAL. The problem is it is an error pointer...
So we can reach this in userspace via fanotify. A filesystem mark on the
lower filesystem of an overlay reports paths on the layer clone and
reading the event hands out a descriptor on it. For example with debugfs
as the lower layer it goes kaboom:
openat(evfd, "tracing", O_DIRECTORY)
Oops: general protection fault
KASAN: null-ptr-deref in range [0x1d0-0x1d7]
RIP: 0010:count_mounts+0x35/0x200
attach_recursive_mnt
finish_automount
And since that sleeping beauty happens under namespace_sem held for
writing every mount operation on the system blocks from then on.
Congrats.
Use is_mounted() instead which rejects unmounted and internal mounts
alike. The open fails with EINVAL just as it did before
clone_private_mount() used MNT_NS_INTERNAL.
Severity
No CVSS data available.
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
df820f8de4e481222b17f9bcee7b909ae8167529 , < 95fb7c259b86f5521f04973040ad492f2bef6f82
(git)
Affected: df820f8de4e481222b17f9bcee7b909ae8167529 , < 35f2013f83ef16f9f0331c4c3a8e8d161580d574 (git) Affected: df820f8de4e481222b17f9bcee7b909ae8167529 , < 494c57572d2d5bc2839553ed41aabe92ed0f587c (git) Affected: df820f8de4e481222b17f9bcee7b909ae8167529 , < 776e20e4fdc23c23687b511ffdc80047878049d3 (git) Affected: df820f8de4e481222b17f9bcee7b909ae8167529 , < ba985ce08471c555af2a2fbe217c1bc2e72a6d8c (git) |
guessed | |
| Linux | Linux |
Affected:
5.8
Unaffected: 0 , < 5.8 (semver) Unaffected: 6.6.160 , ≤ 6.6.* (semver) Unaffected: 6.12.113 , ≤ 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": "95fb7c259b86f5521f04973040ad492f2bef6f82",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "35f2013f83ef16f9f0331c4c3a8e8d161580d574",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "494c57572d2d5bc2839553ed41aabe92ed0f587c",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "776e20e4fdc23c23687b511ffdc80047878049d3",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "ba985ce08471c555af2a2fbe217c1bc2e72a6d8c",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"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": "5.8"
},
{
"lessThan": "5.8",
"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"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.160",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.113",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.57",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.11",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "5.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: refuse an automount below a mount that is in no namespace\n\nIt\u0027s possible to add autmounts even when the parent mount isn\u0027t in the\nmount namespace of the caller. The only requirement we have is that the\nparent mount namespace must not be NULL, i.e., unmounted.\n\nProblem is that clone_private_mount() has MNT_NS_INTERNAL which makes\nthat trivially true. So that passes the test and attach_recursive_mnt()\naccepts that as a mount point and funny enough, count_mounts()\ndereferences MNT_NS_INTERNAL. The problem is it is an error pointer...\n\nSo we can reach this in userspace via fanotify. A filesystem mark on the\nlower filesystem of an overlay reports paths on the layer clone and\nreading the event hands out a descriptor on it. For example with debugfs\nas the lower layer it goes kaboom:\n\n openat(evfd, \"tracing\", O_DIRECTORY)\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x1d0-0x1d7]\n RIP: 0010:count_mounts+0x35/0x200\n attach_recursive_mnt\n finish_automount\n\nAnd since that sleeping beauty happens under namespace_sem held for\nwriting every mount operation on the system blocks from then on.\nCongrats.\n\nUse is_mounted() instead which rejects unmounted and internal mounts\nalike. The open fails with EINVAL just as it did before\nclone_private_mount() used MNT_NS_INTERNAL."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-23T12:19:52.523Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/95fb7c259b86f5521f04973040ad492f2bef6f82"
},
{
"url": "https://git.kernel.org/stable/c/35f2013f83ef16f9f0331c4c3a8e8d161580d574"
},
{
"url": "https://git.kernel.org/stable/c/494c57572d2d5bc2839553ed41aabe92ed0f587c"
},
{
"url": "https://git.kernel.org/stable/c/776e20e4fdc23c23687b511ffdc80047878049d3"
},
{
"url": "https://git.kernel.org/stable/c/ba985ce08471c555af2a2fbe217c1bc2e72a6d8c"
}
],
"title": "namespace: refuse an automount below a mount that is in no namespace",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98979",
"datePublished": "2026-10-23T12:19:52.523Z",
"dateReserved": "2026-09-25T10:25:14.383Z",
"dateUpdated": "2026-10-23T12:19:52.523Z",
"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": "95fb7c259b86f5521f04973040ad492f2bef6f82",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "35f2013f83ef16f9f0331c4c3a8e8d161580d574",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "494c57572d2d5bc2839553ed41aabe92ed0f587c",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "776e20e4fdc23c23687b511ffdc80047878049d3",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"versionType": "git"
},
{
"lessThan": "ba985ce08471c555af2a2fbe217c1bc2e72a6d8c",
"status": "affected",
"version": "df820f8de4e481222b17f9bcee7b909ae8167529",
"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": "5.8"
},
{
"lessThan": "5.8",
"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: refuse an automount below a mount that is in no namespace\n\nIt\u0027s possible to add autmounts even when the parent mount isn\u0027t in the\nmount namespace of the caller. The only requirement we have is that the\nparent mount namespace must not be NULL, i.e., unmounted.\n\nProblem is that clone_private_mount() has MNT_NS_INTERNAL which makes\nthat trivially true. So that passes the test and attach_recursive_mnt()\naccepts that as a mount point and funny enough, count_mounts()\ndereferences MNT_NS_INTERNAL. The problem is it is an error pointer...\n\nSo we can reach this in userspace via fanotify. A filesystem mark on the\nlower filesystem of an overlay reports paths on the layer clone and\nreading the event hands out a descriptor on it. For example with debugfs\nas the lower layer it goes kaboom:\n\n openat(evfd, \"tracing\", O_DIRECTORY)\n\n Oops: general protection fault\n KASAN: null-ptr-deref in range [0x1d0-0x1d7]\n RIP: 0010:count_mounts+0x35/0x200\n attach_recursive_mnt\n finish_automount\n\nAnd since that sleeping beauty happens under namespace_sem held for\nwriting every mount operation on the system blocks from then on.\nCongrats.\n\nUse is_mounted() instead which rejects unmounted and internal mounts\nalike. The open fails with EINVAL just as it did before\nclone_private_mount() used MNT_NS_INTERNAL."
}
],
"id": "CVE-2026-98979",
"lastModified": "2026-10-23T13:17:19.627",
"metrics": {},
"published": "2026-10-23T13:17:19.627",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/35f2013f83ef16f9f0331c4c3a8e8d161580d574"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/494c57572d2d5bc2839553ed41aabe92ed0f587c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/776e20e4fdc23c23687b511ffdc80047878049d3"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/95fb7c259b86f5521f04973040ad492f2bef6f82"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ba985ce08471c555af2a2fbe217c1bc2e72a6d8c"
}
],
"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.