CVE-2026-80758
CVE CVE-2026-80758EUVD EUVD-2026-71401Published 2026-09-04T15:12:27.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: futex: Avoid private hash use-after-free on final put futex_private_hash_put() drops the reference to fph before evaluating fph->mm for wake_up_var(). futex_ref_put() enables preemption again before returning. If that put drops the final reference and the task is preempted, another task can pivot to the replacement hash and free the old hash after an RCU grace period. The first task then reads fph->mm from the freed allocation when it resumes. KASAN reports a slab-use-after-free in futex_private_hash_put(), with the read at offset 24 in a freed kmalloc-512 allocation. The allocation and free stacks point to futex_hash_allocate() and the RCU free path, respectively. Load the mm pointer while the fph reference is still held and pass the saved value to wake_up_var(). wake_up_var() uses the pointer as a waitqueue key and does not dereference the mm through it.
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 bd54df5ea7cadac520e346d5f0fe5d58e635b6ba <1c7efabfbaf796f11000a46094a69955a01ec6cc; bd54df5ea7cadac520e346d5f0fe5d58e635b6ba <12cd315a7b6a7d7db3f69d98bfe3909275e9451d; patch: 6.18.47; bd54df5ea7cadac520e346d5f0fe5d58e635b6ba <dba60d26e9dda3e157ad6b0934d4232f6c6904ee; patch: 0; 6.16; patch: 7.2.1; bd54df5ea7cadac520e346d5f0fe5d58e635b6ba <25408c62ed4ebcd491d0e9e4b4a5b512547512e4; patch: 7.1.11; patch: 7.3-rc1
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.