Answer in brief
CVE-2026-64017 records a Unknown severity vulnerability in blk-mq: pop cached request if it is usable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b0077e269f6c152e807fdac90b58caf012cdbaab <388468f7e7d1eab092cf2a39fdfb502e52019ec6 || >=b0077e269f6c152e807fdac90b58caf012cdbaab <dc278e9bf2b9513a763353e6b9cc21e0f532954e || b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9 || e9c309ded295b7f8849097d71ae231456ca79f78 || b80056bd75a16e4550873ecefe12bc8fd190b1cf || 33cf52b6e53a6aa55883aa7fb9ceffceff8488a6 || 8b6075046470c8756242dfe3fd058813636f69a3 || >=6.1.72 <6.2 || >=6.5.13 <6.6 || >=6.6.3 <6.7 || >=6.1.75 <6.2 || >=6.6.14 <6.7 | 388468f7e7d1eab092cf2a39fdfb502e52019ec6, dc278e9bf2b9513a763353e6b9cc21e0f532954e, 6.2, 6.6, 6.7 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64017 records a Unknown severity vulnerability in blk-mq: pop cached request if it is usable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b0077e269f6c152e807fdac90b58caf012cdbaab <388468f7e7d1eab092cf2a39fdfb502e52019ec6 || >=b0077e269f6c152e807fdac90b58caf012cdbaab <dc278e9bf2b9513a763353e6b9cc21e0f532954e || b5c8e0ff76d10f6bf70a7237678f27c20cf59bc9 || e9c309ded295b7f8849097d71ae231456ca79f78 || b80056bd75a16e4550873ecefe12bc8fd190b1cf || 33cf52b6e53a6aa55883aa7fb9ceffceff8488a6 || 8b6075046470c8756242dfe3fd058813636f69a3 || >=6.1.72 <6.2 || >=6.5.13 <6.6 || >=6.6.3 <6.7 || >=6.1.75 <6.2 || >=6.6.14 <6.7 | 388468f7e7d1eab092cf2a39fdfb502e52019ec6, dc278e9bf2b9513a763353e6b9cc21e0f532954e, 6.2, 6.6, 6.7 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.