{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-98820","id":"CVE-2026-98820","title":"blk-mq: set RQF_USE_SCHED when the operation is known","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: set RQF_USE_SCHED when the operation is known\n\nThe cached requests are allocated for one operation but can be handed\nout for another. A passthrough command has RQF_USE_SCHED cleared, so\nusing those flags for a subsequent read/write bio will insert it into\nthe scheduler without ->prepare_request() and frees it without\n->fi","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: set RQF_USE_SCHED when the operation is known\n\nThe cached requests are allocated for one operation but can be handed\nout for another. A passthrough command has RQF_USE_SCHED cleared, so\nusing those flags for a subsequent read/write bio will insert it into\nthe scheduler without ->prepare_request() and frees it without\n->finish_request(). For kyber, this leaks the domain token acquired at\ndispatch and stalls the queue.\n\nDon't set RQF_USE_SCHED based on the first operation the batch happened\nto be allocated for. Instead, set it after the request is claimed by an\noperation. Introduce a helper function, blk_mq_rq_late_init() for this,\nand absorb blk_mq_rq_time_init() since the two run together.","published":"2026-10-18T15:49:12.251Z","updated":"2026-10-28T02:30:26.237622589Z","reserved":"2026-09-25T10:25:14.372Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"4b6a5d9cea911424e84107df8c4eb8317938d2cd","lessThan":"790730e4d95de8356a573d4b4864486bba731863","status":"affected","versionType":"git"},{"version":"4b6a5d9cea911424e84107df8c4eb8317938d2cd","lessThan":"2c47ebc27fa72078e26177cd458cdaf3006a9685","status":"affected","versionType":"git"},{"version":"4b6a5d9cea911424e84107df8c4eb8317938d2cd","lessThan":"ab6c756f28c741d704a7c3e04814bfc3adf6f818","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.1","status":"affected"},{"version":"0","lessThan":"6.1","status":"unaffected","versionType":"semver"},{"version":"6.18.56","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.2.10","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/790730e4d95de8356a573d4b4864486bba731863","tags":["web"]},{"url":"https://git.kernel.org/stable/c/2c47ebc27fa72078e26177cd458cdaf3006a9685","tags":["web"]},{"url":"https://git.kernel.org/stable/c/ab6c756f28c741d704a7c3e04814bfc3adf6f818","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98820.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98820","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":0.00206,"epssPercentile":0.1092,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-98820","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98820","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-98820","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-98820","ok":true,"note":"scored 2026-11-20"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}