CVE-2026-80758 Affecting kernel6.18-modules-extra-common package, versions <1:6.18.48-107.148.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-AMZN2023-KERNEL618MODULESEXTRACOMMON-20250093
- published29 Sept 2026
- disclosed4 Sept 2026
Introduced: 4 Sep 2026
NewCVE-2026-80758 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 kernel6.18-modules-extra-common to version 1:6.18.48-107.148.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3139.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel6.18-modules-extra-common package and not the kernel6.18-modules-extra-common package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
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.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-80758
- https://git.kernel.org/stable/c/12cd315a7b6a7d7db3f69d98bfe3909275e9451d
- https://git.kernel.org/stable/c/1c7efabfbaf796f11000a46094a69955a01ec6cc
- https://git.kernel.org/stable/c/25408c62ed4ebcd491d0e9e4b4a5b512547512e4
- https://git.kernel.org/stable/c/dba60d26e9dda3e157ad6b0934d4232f6c6904ee