Menu

Star on GitHub · 3.2k

CVE-2026-64017

7.8 · HIGH

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 req…

Published Jul 19, 2026EPSS 0.13%

Overview

CVE-2026-64017 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64017?

CVE-2026-64017 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-64017?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-64017?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64017?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64017 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all