VulnerabilityPublished 25 Jul 2026Updated 17 Aug 2026

CVE-2026-64509: Linux kernel · rust: block: fix GenDisk cleanup paths

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 3 Nov 2026, 18:44 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address the cleanup paths for GenDisk objects in the Rust block subsystem. Users should apply the updated Linux kernel version containing this fix. No additional mitigation steps are indicated.

Description

A memory management issue in the Linux kernel's Rust block subsystem was fixed to properly clean up GenDisk objects and associated request queues during error paths. The flaw caused temporary gendisk and request_queue objects to leak until later teardown, potentially retaining blk-mq state improperly.

Impact

The issue causes resource leaks of temporary gendisk and request_queue objects in the Linux kernel's block subsystem, which could lead to improper release of blk-mq state. While no direct exploitation or active attacks are reported, the leak could affect kernel stability or resource usage.

Summary

The vulnerability in the Linux kernel's Rust block code involves improper cleanup of GenDisk objects in the GenDiskBuilder::build() function. After __blk_mq_alloc_disk(), fallible work remains, but the error path only recovers foreign queue data, leaking temporary gendisk and request_queue objects. This leak can cause the request queue to retain blk-mq state after the tag set is dropped if the caller moved the last Arc<TagSet<T>> into build(). The fix involves dropping the temporary gendisk reference with put_disk() before recovering queue data to allow disk_release() to properly tear down the queue. Additionally, GenDisk::drop() is paired with put_disk() after del_gendisk() to complete the release path once a Rust GenDisk has been added with device_add_disk().

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2026, 18:44 UTC

Technical details

References

Community reviews

Related threats