blk-mq: set RQF_USE_SCHED when the operation is known
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.
CVE-2026-98820
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-98820
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "4b6a5d9cea911424e84107df8c4eb8317938d2cd",
"lessThan": "790730e4d95de8356a573d4b4864486bba731863",
"versionType": "git"
},
{
"status": "affected",
"version": "4b6a5d9cea911424e84107df8c4eb8317938d2cd",
"lessThan": "2c47ebc27fa72078e26177cd458cdaf3006a9685",
"versionType": "git"
},
{
"status": "affected",
"version": "4b6a5d9cea911424e84107df8c4eb8317938d2cd",
"lessThan": "ab6c756f28c741d704a7c3e04814bfc3adf6f818",
"versionType": "git"
}
],
"programFiles": [
"block/blk-mq.c",
"block/mq-deadline.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.1"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.1",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.56",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.10",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"block/blk-mq.c",
"block/mq-deadline.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2026-98820
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #38737 · Revision 1
- Added to Heist Feed
- Publisher date