https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 20:54:24 +0000 https://vulnerability.circl.lu/vuln/cve-2024-57929 <p><strong>Affected:</strong> Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm array: fix releasing a faulty array block twice in dm_array_cursor_end</p> <p>When dm_bm_read_lock() fails due to locking or checksum errors, it releases the faulty block implicitly while leaving an invalid output pointer behind. The caller of dm_bm_read_lock() should not operate on this invalid dm_block pointer, or it will lead to undefined result. For example, the dm_array_cursor incorrectly caches the invalid pointer on reading a faulty array block, causing a double release in dm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put().</p> <p>Reproduce steps:</p> <p>1. initialize a cache device</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; dmsetup create cdata --table &#34;0 65536 linear /dev/sdc 8192&#34; dmsetup create corig --table &#34;0 524288 linear /dev/sdc $262144&#34; dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 dmsetup create cache --table &#34;0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0&#34;</p> <p>2. wipe the second array block offline</p> <p>dmsteup remove cache cmeta cdata corig mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \ 2&gt;/dev/null | hexdump -e &#39;1/8 &#34;%u\n&#34;&#39;) ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \ 2&gt;/dev/null | hexdump -e &#39;1/8 &#34;%u\n&#34;&#39;) dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock</p> <p>3. try reopen the cache device</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; dmsetup create cdata --table…</p> <p><strong>Affected:</strong> Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm array: fix releasing a faulty array block twice in dm_array_cursor_end</p> <p>When dm_bm_read_lock() fails due to locking or checksum errors, it releases the faulty block implicitly while leaving an invalid output pointer behind. The caller of dm_bm_read_lock() should not operate on this invalid dm_block pointer, or it will lead to undefined result. For example, the dm_array_cursor incorrectly caches the invalid pointer on reading a faulty array block, causing a double release in dm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put().</p> <p>Reproduce steps:</p> <p>1. initialize a cache device</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; dmsetup create cdata --table &#34;0 65536 linear /dev/sdc 8192&#34; dmsetup create corig --table &#34;0 524288 linear /dev/sdc $262144&#34; dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 dmsetup create cache --table &#34;0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0&#34;</p> <p>2. wipe the second array block offline</p> <p>dmsteup remove cache cmeta cdata corig mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \ 2&gt;/dev/null | hexdump -e &#39;1/8 &#34;%u\n&#34;&#39;) ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \ 2&gt;/dev/null | hexdump -e &#39;1/8 &#34;%u\n&#34;&#39;) dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock</p> <p>3. try reopen the cache device</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; dmsetup create cdata --table…</p> https://vulnerability.circl.lu/vuln/cve-2024-57929