<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 21:20:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99681 — blk-mq: fix out-of-bounds read in blk_mq_free_rqs</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99681</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-mq: fix out-of-bounds read in blk_mq_free_rqs&lt;/p&gt;
&lt;p&gt;A KASAN slab-out-of-bounds read can occur in blk_mq_free_rqs() when there
is a mismatch between the number of hardware queues allocated for the IO
scheduler (et-&amp;gt;nr_hw_queues) and the number of hardware queues in the block
tag set (set-&amp;gt;nr_hw_queues).&lt;/p&gt;
&lt;p&gt;This mismatch can happen if blk_mq_update_nr_hw_queues() fails halfway
through (e.g., due to memory pressure during
blk_mq_prealloc_tag_set_tags()). In this error path, the elevator is
restored with a larger number of hardware queues than the block tag set
actually has.&lt;/p&gt;
&lt;p&gt;When the elevator is later freed, blk_mq_free_sched_tags() iterates up to
the new et-&amp;gt;nr_hw_queues and calls blk_mq_free_rqs(). In blk_mq_free_rqs(),
it attempts to access set-&amp;gt;tags[hctx_idx] to get the driver tags. Because
set-&amp;gt;nr_hw_queues was not updated due to the earlier failure, set-&amp;gt;tags
still has the old (smaller) size, leading to an out-of-bounds read.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in blk_mq_free_rqs+0xde/0x680
Read of size 8 at addr ffff88818d67fc28 by task syz-executor117/5839
Call Trace:
 blk_mq_free_rqs+0xde/0x680
 blk_mq_free_map_and_rqs+0x40/0xf0
 blk_mq_free_sched_tags
 blk_mq_free_sched_res+0xeb/0x280
 elevator_change_done+0x1d2/0x5c0
 elevator_change+0x34f/0x480
 elv_iosched_store+0x504/0x630
 queue_attr_store+0x207/0x2b0&lt;/p&gt;
&lt;p&gt;To fix this, explicitly check if hctx_idx &amp;lt; set-&amp;gt;nr_hw_queues before
accessing set-&amp;gt;tags[hctx_idx]. I…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;blk-mq: fix out-of-bounds read in blk_mq_free_rqs&lt;/p&gt;
&lt;p&gt;A KASAN slab-out-of-bounds read can occur in blk_mq_free_rqs() when there
is a mismatch between the number of hardware queues allocated for the IO
scheduler (et-&amp;gt;nr_hw_queues) and the number of hardware queues in the block
tag set (set-&amp;gt;nr_hw_queues).&lt;/p&gt;
&lt;p&gt;This mismatch can happen if blk_mq_update_nr_hw_queues() fails halfway
through (e.g., due to memory pressure during
blk_mq_prealloc_tag_set_tags()). In this error path, the elevator is
restored with a larger number of hardware queues than the block tag set
actually has.&lt;/p&gt;
&lt;p&gt;When the elevator is later freed, blk_mq_free_sched_tags() iterates up to
the new et-&amp;gt;nr_hw_queues and calls blk_mq_free_rqs(). In blk_mq_free_rqs(),
it attempts to access set-&amp;gt;tags[hctx_idx] to get the driver tags. Because
set-&amp;gt;nr_hw_queues was not updated due to the earlier failure, set-&amp;gt;tags
still has the old (smaller) size, leading to an out-of-bounds read.&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in blk_mq_free_rqs+0xde/0x680
Read of size 8 at addr ffff88818d67fc28 by task syz-executor117/5839
Call Trace:
 blk_mq_free_rqs+0xde/0x680
 blk_mq_free_map_and_rqs+0x40/0xf0
 blk_mq_free_sched_tags
 blk_mq_free_sched_res+0xeb/0x280
 elevator_change_done+0x1d2/0x5c0
 elevator_change+0x34f/0x480
 elv_iosched_store+0x504/0x630
 queue_attr_store+0x207/0x2b0&lt;/p&gt;
&lt;p&gt;To fix this, explicitly check if hctx_idx &amp;lt; set-&amp;gt;nr_hw_queues before
accessing set-&amp;gt;tags[hctx_idx]. I…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99681</guid>
    </item>
  </channel>
</rss>
