<?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>Wed, 07 Oct 2026 05:50:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53059 — dm log: fix out-of-bounds write due to region_count overflow</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53059</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 8.8 Telecommunications Update Service and 5 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm log: fix out-of-bounds write due to region_count overflow&lt;/p&gt;
&lt;p&gt;The local variable region_count in create_log_context() is declared as
unsigned int (32-bit), but dm_sector_div_up() returns sector_t (64-bit).
When a device-mapper target has a sufficiently large ti-&amp;gt;len with a small
region_size, the division result can exceed UINT_MAX. The truncated
value is then used to calculate bitset_size, causing clean_bits,
sync_bits, and recovering_bits to be allocated far smaller than needed
for the actual number of regions.&lt;/p&gt;
&lt;p&gt;Subsequent log operations (log_set_bit, log_clear_bit, log_test_bit) use
region indices derived from the full untruncated region space, causing
out-of-bounds writes to kernel heap memory allocated by vmalloc.&lt;/p&gt;
&lt;p&gt;This can be reproduced by creating a mirror target whose region_count
overflows 32 bits:&lt;/p&gt;
&lt;p&gt;dmsetup create bigzero --table &amp;#39;0 8589934594 zero&amp;#39;
  dmsetup create mymirror --table &amp;#39;0 8589934594 mirror \
    core 2 2 nosync 2 /dev/mapper/bigzero 0 \
    /dev/mapper/bigzero 0&amp;#39;&lt;/p&gt;
&lt;p&gt;The status output confirms the truncation (sync_count=1 instead of
4294967297, because 0x100000001 was truncated to 1):&lt;/p&gt;
&lt;p&gt;$ dmsetup status mymirror
  0 8589934594 mirror 2 254:1 254:1 1/4294967297 ...&lt;/p&gt;
&lt;p&gt;This leads to a kernel crash in core_in_sync:&lt;/p&gt;
&lt;p&gt;BUG: scheduling while atomic: (udev-worker)/9150/0x00000000
  RIP: 0010:core_in_sync+0x14/0x30 [dm_log]
  CR2: 0000000000000008
  Fixing recursive fault but reboot is needed!…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 8.8 Telecommunications Update Service and 5 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm log: fix out-of-bounds write due to region_count overflow&lt;/p&gt;
&lt;p&gt;The local variable region_count in create_log_context() is declared as
unsigned int (32-bit), but dm_sector_div_up() returns sector_t (64-bit).
When a device-mapper target has a sufficiently large ti-&amp;gt;len with a small
region_size, the division result can exceed UINT_MAX. The truncated
value is then used to calculate bitset_size, causing clean_bits,
sync_bits, and recovering_bits to be allocated far smaller than needed
for the actual number of regions.&lt;/p&gt;
&lt;p&gt;Subsequent log operations (log_set_bit, log_clear_bit, log_test_bit) use
region indices derived from the full untruncated region space, causing
out-of-bounds writes to kernel heap memory allocated by vmalloc.&lt;/p&gt;
&lt;p&gt;This can be reproduced by creating a mirror target whose region_count
overflows 32 bits:&lt;/p&gt;
&lt;p&gt;dmsetup create bigzero --table &amp;#39;0 8589934594 zero&amp;#39;
  dmsetup create mymirror --table &amp;#39;0 8589934594 mirror \
    core 2 2 nosync 2 /dev/mapper/bigzero 0 \
    /dev/mapper/bigzero 0&amp;#39;&lt;/p&gt;
&lt;p&gt;The status output confirms the truncation (sync_count=1 instead of
4294967297, because 0x100000001 was truncated to 1):&lt;/p&gt;
&lt;p&gt;$ dmsetup status mymirror
  0 8589934594 mirror 2 254:1 254:1 1/4294967297 ...&lt;/p&gt;
&lt;p&gt;This leads to a kernel crash in core_in_sync:&lt;/p&gt;
&lt;p&gt;BUG: scheduling while atomic: (udev-worker)/9150/0x00000000
  RIP: 0010:core_in_sync+0x14/0x30 [dm_log]
  CR2: 0000000000000008
  Fixing recursive fault but reboot is needed!…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53059</guid>
    </item>
  </channel>
</rss>
