Answer in brief
CVE-2026-98820 records a Unknown severity vulnerability in blk-mq: set RQF_USE_SCHED when the operation is known. 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 | >=4b6a5d9cea911424e84107df8c4eb8317938d2cd <790730e4d95de8356a573d4b4864486bba731863 || >=4b6a5d9cea911424e84107df8c4eb8317938d2cd <2c47ebc27fa72078e26177cd458cdaf3006a9685 || >=4b6a5d9cea911424e84107df8c4eb8317938d2cd <ab6c756f28c741d704a7c3e04814bfc3adf6f818 | 790730e4d95de8356a573d4b4864486bba731863, 2c47ebc27fa72078e26177cd458cdaf3006a9685, ab6c756f28c741d704a7c3e04814bfc3adf6f818 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: blk-mq: set RQF_USE_SCHED when the operation is known The cached requests are allocated for one operation but can be handed out for another. A passthrough command has RQF_USE_SCHED cleared, so using those flags for a subsequent read/write bio will insert it into the scheduler without ->prepare_request() and frees it without ->finish_request(). For kyber, this leaks the domain token acquired at dispatch and stalls the queue. Don't set RQF_USE_SCHED based on the first operation the batch happened to be allocated for. Instead, set it after the request is claimed by an operation. Introduce a helper function, blk_mq_rq_late_init() for this, and absorb blk_mq_rq_time_init() since the two run together.
Quoted source text, attributed separately from HOL analysis.