CVE-2026-64017

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.

Package Linux Kernel
Published 2026-07-19
Last modified 2026-07-19
Patch available
Yes

Affected versions

Linux kernel versions 6.1.72, 6.5.13, 6.6.3, 6.1.75, 6.6.14, 6.7 and later are affected. Fixed in 7.0.11, 7.1 and their respective stable series.

Affected from
≥ 6.1.72 ≥ 6.5.13 ≥ 6.6.3 ≥ 6.1.75 ≥ 6.6.14 ≥ 6.7
Fixed in
✓ 7.0.11 7.0.x ✓ 7.1

Frequently asked questions

  • What is CVE-2026-64017?

    CVE-2026-64017 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.1.72 onward and has been patched in 7.0.11 and 7.1. CVE-2026-64017 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64017?

    Yes — CVE-2026-64017 has been patched. Fixed versions include 7.0.11 and 7.1. If you are running Linux kernel 6.1.72 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-64017 actively exploited?

    No — CVE-2026-64017 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.