https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 06:21:40 +0000 https://vulnerability.circl.lu/vuln/cve-2026-53060 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm cache metadata: fix memory leak on metadata abort retry</p> <p>When failing to acquire the root_lock in dm_cache_metadata_abort because the block_manager is read-only, the temporary block_manager created outside the root_lock is not properly released, causing a memory leak.</p> <p>Reproduce steps:</p> <p>This can be reproduced by reloading a new table while the metadata is read-only. While the second call to dm_cache_metadata_abort is caused by lack of support for table preload in dm-cache, mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), it exposes the memory leak in dm_cache_metadata_abort when the function is called multiple times. Specifically, dm-cache fails to sync the new cache object&#39;s mode during preresume, creating the reproducer condition.</p> <p>This issue could also occur through concurrent metadata_operation_failed calls due to races in cache mode updates, but the table preload scenario below provides a reliable reproducer.</p> <p>1. Create a cache device with some faulty trailing metadata blocks</p> <p>dmsetup create cmeta &lt;&lt;EOF 0 200 linear /dev/sdc 0 200 7992 error EOF dmsetup create cdata --table &#34;0 131072 linear /dev/sdc 8192&#34; dmsetup create corig --table &#34;0 262144 linear /dev/sdc 262144&#34; dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct dmsetup create cache --table &#34;0 131072 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 1 w…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm cache metadata: fix memory leak on metadata abort retry</p> <p>When failing to acquire the root_lock in dm_cache_metadata_abort because the block_manager is read-only, the temporary block_manager created outside the root_lock is not properly released, causing a memory leak.</p> <p>Reproduce steps:</p> <p>This can be reproduced by reloading a new table while the metadata is read-only. While the second call to dm_cache_metadata_abort is caused by lack of support for table preload in dm-cache, mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), it exposes the memory leak in dm_cache_metadata_abort when the function is called multiple times. Specifically, dm-cache fails to sync the new cache object&#39;s mode during preresume, creating the reproducer condition.</p> <p>This issue could also occur through concurrent metadata_operation_failed calls due to races in cache mode updates, but the table preload scenario below provides a reliable reproducer.</p> <p>1. Create a cache device with some faulty trailing metadata blocks</p> <p>dmsetup create cmeta &lt;&lt;EOF 0 200 linear /dev/sdc 0 200 7992 error EOF dmsetup create cdata --table &#34;0 131072 linear /dev/sdc 8192&#34; dmsetup create corig --table &#34;0 262144 linear /dev/sdc 262144&#34; dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct dmsetup create cache --table &#34;0 131072 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 1 w…</p> https://vulnerability.circl.lu/vuln/cve-2026-53060