<?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://vulnerability.circl.lu</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>Sat, 03 Oct 2026 11:55:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74392 — dm: limit target bio polling to one shot</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74392</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;dm: limit target bio polling to one shot&lt;/p&gt;
&lt;p&gt;dm_poll_bio() is the -&amp;gt;poll_bio() callback for a stacked dm device.
The caller only knows about the dm queue, so it may decide to do a
spinning poll if it thinks a single queue is being polled. Passing those
flags unchanged to the mapped clone lets blk_mq_poll() spin on a target
queue from inside dm_poll_bio().&lt;/p&gt;
&lt;p&gt;With io_uring IOPOLL on a dm-stripe target this can keep a task in&lt;/p&gt;
&lt;p&gt;dm_poll_bio() -&amp;gt; bio_poll() -&amp;gt; blk_mq_poll()&lt;/p&gt;
&lt;p&gt;long enough to trigger an RCU CPU stall, before io_uring gets back to
io_iopoll_check() and its need_resched() check.&lt;/p&gt;
&lt;p&gt;Keep dm&amp;#39;s -&amp;gt;poll_bio() bounded by forcing one-shot polling for target
bios. The caller can invoke dm_poll_bio() again if it wants to keep
polling, and it also gets a chance to reap completions or reschedule
between passes.&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;dm: limit target bio polling to one shot&lt;/p&gt;
&lt;p&gt;dm_poll_bio() is the -&amp;gt;poll_bio() callback for a stacked dm device.
The caller only knows about the dm queue, so it may decide to do a
spinning poll if it thinks a single queue is being polled. Passing those
flags unchanged to the mapped clone lets blk_mq_poll() spin on a target
queue from inside dm_poll_bio().&lt;/p&gt;
&lt;p&gt;With io_uring IOPOLL on a dm-stripe target this can keep a task in&lt;/p&gt;
&lt;p&gt;dm_poll_bio() -&amp;gt; bio_poll() -&amp;gt; blk_mq_poll()&lt;/p&gt;
&lt;p&gt;long enough to trigger an RCU CPU stall, before io_uring gets back to
io_iopoll_check() and its need_resched() check.&lt;/p&gt;
&lt;p&gt;Keep dm&amp;#39;s -&amp;gt;poll_bio() bounded by forcing one-shot polling for target
bios. The caller can invoke dm_poll_bio() again if it wants to keep
polling, and it also gets a chance to reap completions or reschedule
between passes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74392</guid>
    </item>
  </channel>
</rss>
