<?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>Tue, 29 Sep 2026 06:55:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53860 — dm: don't attempt to queue IO under RCU protection</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53860</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: don&amp;#39;t attempt to queue IO under RCU protection&lt;/p&gt;
&lt;p&gt;dm looks up the table for IO based on the request type, with an
assumption that if the request is marked REQ_NOWAIT, it&amp;#39;s fine to
attempt to submit that IO while under RCU read lock protection. This
is not OK, as REQ_NOWAIT just means that we should not be sleeping
waiting on other IO, it does not mean that we can&amp;#39;t potentially
schedule.&lt;/p&gt;
&lt;p&gt;A simple test case demonstrates this quite nicely:&lt;/p&gt;
&lt;p&gt;int main(int argc, char *argv[])
{
        struct iovec iov;
        int fd;&lt;/p&gt;
&lt;p&gt;fd = open(&amp;#34;/dev/dm-0&amp;#34;, O_RDONLY | O_DIRECT);
        posix_memalign(&amp;amp;iov.iov_base, 4096, 4096);
        iov.iov_len = 4096;
        preadv2(fd, &amp;amp;iov, 1, 0, RWF_NOWAIT);
        return 0;
}&lt;/p&gt;
&lt;p&gt;which will instantly spew:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at include/linux/sched/mm.h:306
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 5580, name: dm-nowait
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
CPU: 7 PID: 5580 Comm: dm-nowait Not tainted 6.6.0-rc1-g39956d2dcd81 #132
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0x11d/0x1b0
 __might_resched+0x3c3/0x5e0
 ? preempt_count_sub+0x150/0x150
 mempool_alloc+0x1e2/0x390
 ? mempool_resize+0x7d0/0x7d0
 ? lock_sync+0x190/0x190
 ? lock_release+0x4b7/0x670
 ? internal_get_user_pages_fast+0x868/0x2d4…&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: don&amp;#39;t attempt to queue IO under RCU protection&lt;/p&gt;
&lt;p&gt;dm looks up the table for IO based on the request type, with an
assumption that if the request is marked REQ_NOWAIT, it&amp;#39;s fine to
attempt to submit that IO while under RCU read lock protection. This
is not OK, as REQ_NOWAIT just means that we should not be sleeping
waiting on other IO, it does not mean that we can&amp;#39;t potentially
schedule.&lt;/p&gt;
&lt;p&gt;A simple test case demonstrates this quite nicely:&lt;/p&gt;
&lt;p&gt;int main(int argc, char *argv[])
{
        struct iovec iov;
        int fd;&lt;/p&gt;
&lt;p&gt;fd = open(&amp;#34;/dev/dm-0&amp;#34;, O_RDONLY | O_DIRECT);
        posix_memalign(&amp;amp;iov.iov_base, 4096, 4096);
        iov.iov_len = 4096;
        preadv2(fd, &amp;amp;iov, 1, 0, RWF_NOWAIT);
        return 0;
}&lt;/p&gt;
&lt;p&gt;which will instantly spew:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at include/linux/sched/mm.h:306
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 5580, name: dm-nowait
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
CPU: 7 PID: 5580 Comm: dm-nowait Not tainted 6.6.0-rc1-g39956d2dcd81 #132
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 &amp;lt;TASK&amp;gt;
 dump_stack_lvl+0x11d/0x1b0
 __might_resched+0x3c3/0x5e0
 ? preempt_count_sub+0x150/0x150
 mempool_alloc+0x1e2/0x390
 ? mempool_resize+0x7d0/0x7d0
 ? lock_sync+0x190/0x190
 ? lock_release+0x4b7/0x670
 ? internal_get_user_pages_fast+0x868/0x2d4…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53860</guid>
    </item>
  </channel>
</rss>
