Kernel memory corruption via dangling timeout timer
Published Aug 26, 2026 · Updated Aug 26, 2026
Use-after-free in the Linux kernel block layer allows remote attackers to corrupt kernel memory through crafted NVMe-oF responses. disk_release() frees a request_queue after a pre-add_disk probe failure without stopping q->timeout, leaving its timer-wheel entry to access freed memory. An attacker must control an established NVMe fabric endpoint and induce namespace I/O plus probe failure; consequences include kernel disclosure, arbitrary writes, or a panic.
Summary
What happened
Use-after-free in the Linux kernel block layer allows remote attackers to corrupt kernel memory through crafted NVMe-oF responses. disk_release() frees a request_queue after a pre-add_disk probe failure without stopping q->timeout, leaving its timer-wheel entry to access freed memory. An attacker must control an established NVMe fabric endpoint and induce namespace I/O plus probe failure; consequences include kernel disclosure, arbitrary writes, or a panic.
The record
- CVE
- CVE-2026-80589
- Published
- Aug 26, 2026
- Updated
- Aug 26, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-825, CWE-416, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.19.12 <5.20
- Affected versionversion=6.0
- Affected versionversion=6f8191fdf41d3a53cc1d63fe2234e812c55a0092 <1a0ae4d502062a2759f2a92d12bdeab3c64c7372
- Affected versionversion=6f8191fdf41d3a53cc1d63fe2234e812c55a0092 <26cb8ebbfaf713c82e142d08828d4d765057633b
- Affected versionversion=6f8191fdf41d3a53cc1d63fe2234e812c55a0092 <6ae7364f68e6c7af6b6df4bbb14040b89e5975d0
- Affected versionversion=6f8191fdf41d3a53cc1d63fe2234e812c55a0092 <6f06dbe5012c160e0dba418a5a9cb16c456ad46a
- Affected versionversion=6f8191fdf41d3a53cc1d63fe2234e812c55a0092 <93d620519d71dfc6ee64b5baea74f1d85d4439fb
- Affected versionversion=6f8191fdf41d3a53cc1d63fe2234e812c55a0092 <bb03b56d1d754908a37a160603be21769da423cf
- Affected versionversion=d27b66257db183fe11c10f31246ae965adb005d3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo