CVE-2026-64017

blk-mq: pop cached request if it is usable

HIGH
7.8
CVSS Score
Published: July 19, 2026 at 03:39 PM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: blk-mq: pop cached request if it is usable When submitting a bio to blk-mq, if the task should sleep after peeking a cached request, but before it pops it, the plug flushes and calls blk_mq_free_plug_rqs, freeing the cached_rqs. This creates a use-after-free bug. Fix this by popping the cached request before any possible blocking calls if it is suitable for use. Popping this request first holds a queue reference, so avoid any serialization races with queue freezes and can safely proceed with dispatching that request to the driver. This potentially increases a timing window from when a driver wants to freeze its queue to when requests stop being dispatched. That scenario is off the fast path though, and drivers need to appropriately handle requests during a freeze request anyway. The downside is the popped element needs to be individually freed when we performed a bio plug merge. The cached request would have had to be freed later anyway, but this patch does it inline with building the plug list instead of after flushing it.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.72 ≤ v < 6.26.1.75 ≤ v < 6.26.13 ≤ v < 6.18.456.19 ≤ v < 7.0.116.5.13 ≤ v < 6.66.6.14 ≤ v < 6.76.6.3 ≤ v < 6.76.7.1 ≤ v < 6.12.10433cf52b6e53a6aa55883aa7fb9ceffceff8488a66.1.726.1.756.5.136.6.146.6.36.77.18b6075046470c8756242dfe3fd058813636f69a3b0077e269f6c152e807fdac90b58caf012cdbaabb5c8e0ff76d10f6bf70a7237678f27c20cf59bc9b80056bd75a16e4550873ecefe12bc8fd190b1cfe9c309ded295b7f8849097d71ae231456ca79f78
Vendor states this is fixed in 23d8ea1e303b5f32d883757a4a707e791dbc9808 (fixed)
Vendor states this is fixed in 388468f7e7d1eab092cf2a39fdfb502e52019ec6 (fixed)
Vendor states this is fixed in 97e2d08de282ef76f84ab4ccd00f1acb3f5f999e (fixed)
Vendor states this is fixed in dc278e9bf2b9513a763353e6b9cc21e0f532954e (fixed)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 7.0.11 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card