<?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://127.0.0.1:10001</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, 21 Nov 2026 11:31:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53062 — dm cache policy smq: fix missing locks in invalidating cache blocks</title>
      <link>https://127.0.0.1:10001/vuln/cve-2026-53062</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 cache policy smq: fix missing locks in invalidating cache blocks&lt;/p&gt;
&lt;p&gt;In passthrough mode, the policy invalidate_mapping operation is called
simultaneously from multiple workers, thus it should be protected by a
lock. Otherwise, we might end up with data races on the allocated blocks
counter, or even use-after-free issues with internal data structures
when doing concurrent writes.&lt;/p&gt;
&lt;p&gt;Note that the existing FIXME in smq_invalidate_mapping() doesn&amp;#39;t affect
passthrough mode since migration tasks don&amp;#39;t exist there, but would need
attention if supporting fast device shrinking via suspend/resume without
target reloading.&lt;/p&gt;
&lt;p&gt;Reproduce steps:&lt;/p&gt;
&lt;p&gt;1. Create a cache device consisting of 1024 cache entries&lt;/p&gt;
&lt;p&gt;dmsetup create cmeta --table &amp;#34;0 8192 linear /dev/sdc 0&amp;#34;
dmsetup create cdata --table &amp;#34;0 131072 linear /dev/sdc 8192&amp;#34;
dmsetup create corig --table &amp;#34;0 262144 linear /dev/sdc 262144&amp;#34;
dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct
dmsetup create cache --table &amp;#34;0 262144 cache /dev/mapper/cmeta \
/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0&amp;#34;&lt;/p&gt;
&lt;p&gt;2. Populate the cache, and record the number of cached blocks&lt;/p&gt;
&lt;p&gt;fio --name=populate --filename=/dev/mapper/cache --rw=randwrite --bs=4k \
--size=64m --direct=1
nr_cached=$(dmsetup status cache | awk &amp;#39;{split($7, a, &amp;#34;/&amp;#34;); print a[1]}&amp;#39;)&lt;/p&gt;
&lt;p&gt;3. Reload the cache into passthrough mode&lt;/p&gt;
&lt;p&gt;dmsetup suspend cache
dmsetup reload cache --table &amp;#34;0 262144 cache /dev/m…&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 cache policy smq: fix missing locks in invalidating cache blocks&lt;/p&gt;
&lt;p&gt;In passthrough mode, the policy invalidate_mapping operation is called
simultaneously from multiple workers, thus it should be protected by a
lock. Otherwise, we might end up with data races on the allocated blocks
counter, or even use-after-free issues with internal data structures
when doing concurrent writes.&lt;/p&gt;
&lt;p&gt;Note that the existing FIXME in smq_invalidate_mapping() doesn&amp;#39;t affect
passthrough mode since migration tasks don&amp;#39;t exist there, but would need
attention if supporting fast device shrinking via suspend/resume without
target reloading.&lt;/p&gt;
&lt;p&gt;Reproduce steps:&lt;/p&gt;
&lt;p&gt;1. Create a cache device consisting of 1024 cache entries&lt;/p&gt;
&lt;p&gt;dmsetup create cmeta --table &amp;#34;0 8192 linear /dev/sdc 0&amp;#34;
dmsetup create cdata --table &amp;#34;0 131072 linear /dev/sdc 8192&amp;#34;
dmsetup create corig --table &amp;#34;0 262144 linear /dev/sdc 262144&amp;#34;
dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct
dmsetup create cache --table &amp;#34;0 262144 cache /dev/mapper/cmeta \
/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0&amp;#34;&lt;/p&gt;
&lt;p&gt;2. Populate the cache, and record the number of cached blocks&lt;/p&gt;
&lt;p&gt;fio --name=populate --filename=/dev/mapper/cache --rw=randwrite --bs=4k \
--size=64m --direct=1
nr_cached=$(dmsetup status cache | awk &amp;#39;{split($7, a, &amp;#34;/&amp;#34;); print a[1]}&amp;#39;)&lt;/p&gt;
&lt;p&gt;3. Reload the cache into passthrough mode&lt;/p&gt;
&lt;p&gt;dmsetup suspend cache
dmsetup reload cache --table &amp;#34;0 262144 cache /dev/m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cve-2026-53062</guid>
    </item>
  </channel>
</rss>
