{"id":"CVE-2026-99681","summary":"blk-mq: fix out-of-bounds read in blk_mq_free_rqs","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: fix out-of-bounds read in blk_mq_free_rqs\n\nA KASAN slab-out-of-bounds read can occur in blk_mq_free_rqs() when there\nis a mismatch between the number of hardware queues allocated for the IO\nscheduler (et-\u003enr_hw_queues) and the number of hardware queues in the block\ntag set (set-\u003enr_hw_queues).\n\nThis mismatch can happen if blk_mq_update_nr_hw_queues() fails halfway\nthrough (e.g., due to memory pressure during\nblk_mq_prealloc_tag_set_tags()). In this error path, the elevator is\nrestored with a larger number of hardware queues than the block tag set\nactually has.\n\nWhen the elevator is later freed, blk_mq_free_sched_tags() iterates up to\nthe new et-\u003enr_hw_queues and calls blk_mq_free_rqs(). In blk_mq_free_rqs(),\nit attempts to access set-\u003etags[hctx_idx] to get the driver tags. Because\nset-\u003enr_hw_queues was not updated due to the earlier failure, set-\u003etags\nstill has the old (smaller) size, leading to an out-of-bounds read.\n\nBUG: KASAN: slab-out-of-bounds in blk_mq_free_rqs+0xde/0x680\nRead of size 8 at addr ffff88818d67fc28 by task syz-executor117/5839\nCall Trace:\n blk_mq_free_rqs+0xde/0x680\n blk_mq_free_map_and_rqs+0x40/0xf0\n blk_mq_free_sched_tags\n blk_mq_free_sched_res+0xeb/0x280\n elevator_change_done+0x1d2/0x5c0\n elevator_change+0x34f/0x480\n elv_iosched_store+0x504/0x630\n queue_attr_store+0x207/0x2b0\n\nTo fix this, explicitly check if hctx_idx \u003c set-\u003enr_hw_queues before\naccessing set-\u003etags[hctx_idx]. If hctx_idx \u003e= set-\u003enr_hw_queues, the\nhardware queue doesn't exist in the tag set, meaning there are no driver\ntags to clear mappings from. In this case, safely set drv_tags to NULL. The\nsubsequent call to blk_mq_clear_rq_mapping() already handles a NULL\ndrv_tags pointer and will safely return.","modified":"2026-11-20T07:01:07.741485766Z","published":"2026-11-20T05:50:27.952Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99681.json","cna_assigner":"Linux"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/894e4e6084924cfd590968d45fad20908e02ddae"},{"type":"WEB","url":"https://git.kernel.org/stable/c/92ea40ca224ca9909dc7a5ac80dfb3e7cb0e6cae"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a66d71dddc041ddf02c0476778573c5dba30f758"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99681.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99681"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"04225d13aef11b2a539014def5e47d8c21fd74a5"},{"fixed":"a66d71dddc041ddf02c0476778573c5dba30f758"},{"fixed":"92ea40ca224ca9909dc7a5ac80dfb3e7cb0e6cae"},{"fixed":"894e4e6084924cfd590968d45fad20908e02ddae"}]},{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"e01facfb54a9b2e1ad7bbb00601a42b16d276d81"}]}],"versions":["v6.16.12","v6.16.11","v6.16.10","v6.16.9","v6.16.8","v6.16.7","v6.16.6","v6.16.5","v6.16.4"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99681.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.16.4"},{"fixed":"6.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.17.0"},{"fixed":"6.18.64"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99681.json"}}],"schema_version":"1.9.2"}