CVE-2026-72034 (GCVE-0-2026-72034)
Vulnerability from cvelistv5
Published
2026-08-15 05:51
Modified
2026-08-17 05:39
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
fhandle: reject detached mounts in capable_wrt_mount()
The recent fhandle RCU fix moved the mount namespace capability check
into capable_wrt_mount(), so a non-NULL mnt_namespace survives the
ns_capable() dereference. The helper still assumes the later
READ_ONCE(mount->mnt_ns) must be non-NULL because may_decode_fh()
checked is_mounted() first.
That assumption is not stable. A detached mount from
open_tree(..., OPEN_TREE_CLONE) can be dissolved on fput while
open_by_handle_at() is between those checks, and umount_tree() can
clear mount->mnt_ns. If the helper observes NULL, it dereferences
mnt_ns->user_ns and panics.
Return false when the RCU read observes a detached mount. This keeps
the relaxed permission path conservative: a mount no longer attached
to a namespace cannot authorize open_by_handle_at() access.
References
| URL | Tags | |
|---|---|---|
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/fhandle.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "15104234c267ebe04b9f9a73e5c2179cc265ff60",
"status": "affected",
"version": "620c266f394932e5decc4b34683a75dfc59dc2f4",
"versionType": "git"
},
{
"lessThan": "6c52226072a3c61337b1eec1799bb987748884fa",
"status": "affected",
"version": "620c266f394932e5decc4b34683a75dfc59dc2f4",
"versionType": "git"
},
{
"lessThan": "6ee183d89261bf1d1cf9f06d80a40dab8f36ee55",
"status": "affected",
"version": "620c266f394932e5decc4b34683a75dfc59dc2f4",
"versionType": "git"
},
{
"lessThan": "6c732471740bc2ac9b0946134f9f551dc75f4369",
"status": "affected",
"version": "620c266f394932e5decc4b34683a75dfc59dc2f4",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/fhandle.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.11"
},
{
"lessThan": "6.11",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.97",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.40",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.97",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.40",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "6.11",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfhandle: reject detached mounts in capable_wrt_mount()\n\nThe recent fhandle RCU fix moved the mount namespace capability check\ninto capable_wrt_mount(), so a non-NULL mnt_namespace survives the\nns_capable() dereference. The helper still assumes the later\nREAD_ONCE(mount-\u003emnt_ns) must be non-NULL because may_decode_fh()\nchecked is_mounted() first.\n\nThat assumption is not stable. A detached mount from\nopen_tree(..., OPEN_TREE_CLONE) can be dissolved on fput while\nopen_by_handle_at() is between those checks, and umount_tree() can\nclear mount-\u003emnt_ns. If the helper observes NULL, it dereferences\nmnt_ns-\u003euser_ns and panics.\n\nReturn false when the RCU read observes a detached mount. This keeps\nthe relaxed permission path conservative: a mount no longer attached\nto a namespace cannot authorize open_by_handle_at() access."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - Exploitation requires local syscalls only: open_tree(OPEN_TREE_CLONE) to obtain a detached mount fd, open_by_handle_at() to enter may_decode_fh()/capable_wrt_mount(), and close()/fput to dissolve the mount; no network, adjacent, or physical interface reaches this VFS fhandle path.\nAC:L - The attacker controls both sides of the TOCTOU race by concurrently calling open_by_handle_at() on a detached mount fd while another thread closes that fd (or a dup) to trigger dissolve_on_fput()/umount_tree() clearing mount-\u003emnt_ns, making success depend on attacker timing rather than external state.\nPR:L - The relaxed permission path requires CAP_SYS_ADMIN in the current mount namespace (may_mount/open_tree) and CAP_DAC_READ_SEARCH in the current user namespace while lacking init_user_ns CAP_DAC_READ_SEARCH; these are obtainable by an unprivileged local user via user/mount namespaces (unshare -Urn), not real init-namespace root.\nUI:N - No victim action is required; the attacker creates the detached mount, supplies the file handle, and drives the concurrent open_by_handle_at()/close race entirely through their own syscalls and threads.\nS:U - Impact is confined to kernel memory/availability within the same security authority (local/container-triggered kernel panic or namespace lifetime corruption); it does not cross a VM escape, sandbox, or IOMMU boundary per kernel CVSS scope guidance.\nC:H - The affected window (since 620c266f3949) includes unsynchronized mount::mnt_ns access that can UAF freed mnt_namespace memory before the RCU fix, and later NULL/stale namespace dereferences; per kernel guidance UAF and mount-namespace lifetime races enable arbitrary kernel memory disclosure.\nI:H - Concurrent umount_tree() clearing mount-\u003emnt_ns while capable_wrt_mount() dereferences mnt_ns-\u003euser_ns is a mount-namespace lifetime corruption bug; UAF in the same code path can be leveraged for heap corruption and arbitrary kernel writes/code execution, not merely a benign error return.\nA:H - Observing NULL or freed mnt_ns during ns_capable(mnt_ns-\u003euser_ns, CAP_SYS_ADMIN) causes a kernel oops/panic; the race is repeatable by reopening detached mounts, enabling reliable host DoS from containerized tenants on multi-tenant cloud nodes."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:39:37.172Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/15104234c267ebe04b9f9a73e5c2179cc265ff60"
},
{
"url": "https://git.kernel.org/stable/c/6c52226072a3c61337b1eec1799bb987748884fa"
},
{
"url": "https://git.kernel.org/stable/c/6ee183d89261bf1d1cf9f06d80a40dab8f36ee55"
},
{
"url": "https://git.kernel.org/stable/c/6c732471740bc2ac9b0946134f9f551dc75f4369"
}
],
"title": "fhandle: reject detached mounts in capable_wrt_mount()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72034",
"datePublished": "2026-08-15T05:51:55.739Z",
"dateReserved": "2026-08-09T03:40:39.901Z",
"dateUpdated": "2026-08-17T05:39:37.172Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…