{"api_version":"1","generated_at":"2026-10-21T10:17:08+00:00","cve":"CVE-2026-98820","urls":{"html":"https://cve.report/CVE-2026-98820","api":"https://cve.report/api/cve/CVE-2026-98820.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98820","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98820"},"summary":{"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->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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:36","updated_at":"2026-10-19 10:19:46"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/ab6c756f28c741d704a7c3e04814bfc3adf6f818","name":"https://git.kernel.org/stable/c/ab6c756f28c741d704a7c3e04814bfc3adf6f818","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2c47ebc27fa72078e26177cd458cdaf3006a9685","name":"https://git.kernel.org/stable/c/2c47ebc27fa72078e26177cd458cdaf3006a9685","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/790730e4d95de8356a573d4b4864486bba731863","name":"https://git.kernel.org/stable/c/790730e4d95de8356a573d4b4864486bba731863","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98820","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98820","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4b6a5d9cea911424e84107df8c4eb8317938d2cd 790730e4d95de8356a573d4b4864486bba731863 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4b6a5d9cea911424e84107df8c4eb8317938d2cd 2c47ebc27fa72078e26177cd458cdaf3006a9685 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4b6a5d9cea911424e84107df8c4eb8317938d2cd ab6c756f28c741d704a7c3e04814bfc3adf6f818 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.56 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.10 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["block/blk-mq.c","block/mq-deadline.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"790730e4d95de8356a573d4b4864486bba731863","status":"affected","version":"4b6a5d9cea911424e84107df8c4eb8317938d2cd","versionType":"git"},{"lessThan":"2c47ebc27fa72078e26177cd458cdaf3006a9685","status":"affected","version":"4b6a5d9cea911424e84107df8c4eb8317938d2cd","versionType":"git"},{"lessThan":"ab6c756f28c741d704a7c3e04814bfc3adf6f818","status":"affected","version":"4b6a5d9cea911424e84107df8c4eb8317938d2cd","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["block/blk-mq.c","block/mq-deadline.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.1"},{"lessThan":"6.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.56","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.56","versionStartIncluding":"6.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.10","versionStartIncluding":"6.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:26:13.210Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/790730e4d95de8356a573d4b4864486bba731863"},{"url":"https://git.kernel.org/stable/c/2c47ebc27fa72078e26177cd458cdaf3006a9685"},{"url":"https://git.kernel.org/stable/c/ab6c756f28c741d704a7c3e04814bfc3adf6f818"}],"title":"blk-mq: set RQF_USE_SCHED when the operation is known","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98820","datePublished":"2026-10-18T15:49:12.251Z","dateReserved":"2026-09-25T10:25:14.372Z","dateUpdated":"2026-10-19T09:26:13.210Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:36","lastModifiedDate":"2026-10-19 10:19:46","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98820","Ordinal":"1","Title":"blk-mq: set RQF_USE_SCHED when the operation is known","CVE":"CVE-2026-98820","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98820","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"blk-mq: set RQF_USE_SCHED when the operation is known"}]}}}