CVE-2026-72034
CVE CVE-2026-72034EUVD EUVD-2026-58992Published 2026-08-15T05:51:55.000ZLast changed 2026-08-17T05:39:37.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.97; 620c266f394932e5decc4b34683a75dfc59dc2f4 <6ee183d89261bf1d1cf9f06d80a40dab8f36ee55; 6.11; patch: 7.2; patch: 7.1.5; 620c266f394932e5decc4b34683a75dfc59dc2f4 <6c732471740bc2ac9b0946134f9f551dc75f4369; patch: 6.18.40; patch: 0; 620c266f394932e5decc4b34683a75dfc59dc2f4 <6c52226072a3c61337b1eec1799bb987748884fa; 620c266f394932e5decc4b34683a75dfc59dc2f4 <15104234c267ebe04b9f9a73e5c2179cc265ff60
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.