CVE-2026-98820: Linux kernel · blk-mq: set RQF_USE_SCHED when the operation is known
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ab6c756f28c741d704a7c3e04814bfc3adf6f818 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ab6c756f28c741d704a7c3e04814bfc3adf6f818, 790730e4d95de8356a573d4b4864486bba731863, 2c47ebc27fa72078e26177cd458cdaf3006a9685
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to ab6c756f28c741d704a7c3e04814bfc3adf6f818, 790730e4d95de8356a573d4b4864486bba731863 or 2c47ebc27fa72078e26177cd458cdaf3006a9685.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel as indicated by the fixed commit versions. Users should update to a kernel version that includes the patches identified by commits ab6c756f28c741d704a7c3e04814bfc3adf6f818, 790730e4d95de8356a573d4b4864486bba731863, or 2c47ebc27fa72078e26177cd458cdaf3006a9685 to remediate this issue.
Description
A vulnerability in the Linux kernel's blk-mq subsystem involves improper setting of the RQF_USE_SCHED flag when reusing cached requests for different operations. This flaw can cause domain token leaks and queue stalls in the kyber scheduler. The issue is fixed by setting RQF_USE_SCHED only after the request is claimed by an operation, using a new helper function blk_mq_rq_late_init().