https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 10:12:27 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-53061 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-53061 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862 certfr-2026-avi-0862 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862 https://cve.radiocsirt.org/vuln/euvd-2026-329958 EUVD-2026-329958 https://cve.radiocsirt.org/vuln/euvd-2026-329958 https://cve.radiocsirt.org/vuln/fkie_cve-2026-53061 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm cache: fix dirty mapping checking in passthrough mode switching</p> <p>As mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), dm-cache assumed table reload occurs after suspension, while LVM&#39;s table preload breaks this assumption. The dirty mapping check for passthrough mode was designed around this assumption and is performed during table creation, causing the check to fail with preload while metadata updates are ongoing. This risks loading dirty mappings into passthrough mode, resulting in data loss.</p> <p>Reproduce steps:</p> <p>1. Create a writeback cache with zero migration_threshold to produce dirty mappings</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; 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 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ 2 migration_threshold 0&#34;</p> <p>2. Preload a table in passthrough mode</p> <p>dmsetup reload cache --table &#34;0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0&#34;</p> <p>3. Write to the first cache block to make it dirty</p> <p>fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k</p> <p>4. Resume the inactive table. No…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm cache: fix dirty mapping checking in passthrough mode switching</p> <p>As mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), dm-cache assumed table reload occurs after suspension, while LVM&#39;s table preload breaks this assumption. The dirty mapping check for passthrough mode was designed around this assumption and is performed during table creation, causing the check to fail with preload while metadata updates are ongoing. This risks loading dirty mappings into passthrough mode, resulting in data loss.</p> <p>Reproduce steps:</p> <p>1. Create a writeback cache with zero migration_threshold to produce dirty mappings</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; 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 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ 2 migration_threshold 0&#34;</p> <p>2. Preload a table in passthrough mode</p> <p>dmsetup reload cache --table &#34;0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0&#34;</p> <p>3. Write to the first cache block to make it dirty</p> <p>fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k</p> <p>4. Resume the inactive table. No…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-53061 https://cve.radiocsirt.org/vuln/ghsa-h3w6-62jw-v8p3 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm cache: fix dirty mapping checking in passthrough mode switching</p> <p>As mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), dm-cache assumed table reload occurs after suspension, while LVM&#39;s table preload breaks this assumption. The dirty mapping check for passthrough mode was designed around this assumption and is performed during table creation, causing the check to fail with preload while metadata updates are ongoing. This risks loading dirty mappings into passthrough mode, resulting in data loss.</p> <p>Reproduce steps:</p> <p>1. Create a writeback cache with zero migration_threshold to produce dirty mappings</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; 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 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ 2 migration_threshold 0&#34;</p> <p>2. Preload a table in passthrough mode</p> <p>dmsetup reload cache --table &#34;0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0&#34;</p> <p>3. Write to the first cache block to make it dirty</p> <p>fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k</p> <p>4. Resume the inactive table. No…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm cache: fix dirty mapping checking in passthrough mode switching</p> <p>As mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), dm-cache assumed table reload occurs after suspension, while LVM&#39;s table preload breaks this assumption. The dirty mapping check for passthrough mode was designed around this assumption and is performed during table creation, causing the check to fail with preload while metadata updates are ongoing. This risks loading dirty mappings into passthrough mode, resulting in data loss.</p> <p>Reproduce steps:</p> <p>1. Create a writeback cache with zero migration_threshold to produce dirty mappings</p> <p>dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; 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 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ 2 migration_threshold 0&#34;</p> <p>2. Preload a table in passthrough mode</p> <p>dmsetup reload cache --table &#34;0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0&#34;</p> <p>3. Write to the first cache block to make it dirty</p> <p>fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k</p> <p>4. Resume the inactive table. No…</p> https://cve.radiocsirt.org/vuln/ghsa-h3w6-62jw-v8p3 https://cve.radiocsirt.org/vuln/msrc_cve-2026-53061 msrc_CVE-2026-53061 https://cve.radiocsirt.org/vuln/msrc_cve-2026-53061 https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53061 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 253 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dm cache: fix dirty mapping checking in passthrough mode switching As mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), dm-cache assumed table reload occurs after suspension, while LVM&#39;s table preload breaks this assumption. The dirty mapping check for passthrough mode was designed around this assumption and is performed during table creation, causing the check to fail with preload while metadata updates are ongoing. This risks loading dirty mappings into passthrough mode, resulting in data loss. Reproduce steps: 1. Create a writeback cache with zero migration_threshold to produce dirty mappings dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; 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 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ 2 migration_threshold 0&#34; 2. Preload a table in passthrough mode dmsetup reload cache --table &#34;0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0&#34; 3. Write to the first cache block to make it dirty fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k 4. Resume the inactive table. Now it&#39;s pos…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 253 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dm cache: fix dirty mapping checking in passthrough mode switching As mentioned in commit 9b1cc9f251af (&#34;dm cache: share cache-metadata object across inactive and active DM tables&#34;), dm-cache assumed table reload occurs after suspension, while LVM&#39;s table preload breaks this assumption. The dirty mapping check for passthrough mode was designed around this assumption and is performed during table creation, causing the check to fail with preload while metadata updates are ongoing. This risks loading dirty mappings into passthrough mode, resulting in data loss. Reproduce steps: 1. Create a writeback cache with zero migration_threshold to produce dirty mappings dmsetup create cmeta --table &#34;0 8192 linear /dev/sdc 0&#34; 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 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writeback smq \ 2 migration_threshold 0&#34; 2. Preload a table in passthrough mode dmsetup reload cache --table &#34;0 262144 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 passthrough smq 0&#34; 3. Write to the first cache block to make it dirty fio --filename=/dev/mapper/cache --name=populate --rw=write --bs=4k \ --direct=1 --size=64k 4. Resume the inactive table. Now it&#39;s pos…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53061 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077 <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077