https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 13:19:07 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-08848 bdu:2026-08848 https://cve.radiocsirt.org/vuln/bdu:2026-08848 https://cve.radiocsirt.org/vuln/bell-cve-2025-71161 <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-2025-71161 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/euvd-2026-364626 EUVD-2026-364626 https://cve.radiocsirt.org/vuln/euvd-2026-364626 https://cve.radiocsirt.org/vuln/fkie_cve-2025-71161 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-verity: disable recursive forward error correction</p> <p>There are two problems with the recursive correction:</p> <p>1. It may cause denial-of-service. In fec_read_bufs, there is a loop that has 253 iterations. For each iteration, we may call verity_hash_for_block recursively. There is a limit of 4 nested recursions - that means that there may be at most 253^4 (4 billion) iterations. Red Hat QE team actually created an image that pushes dm-verity to this limit - and this image just makes the udev-worker process get stuck in the &#39;D&#39; state.</p> <p>2. It doesn&#39;t work. In fec_read_bufs we store data into the variable &#34;fio-&gt;bufs&#34;, but fio bufs is shared between recursive invocations, if &#34;verity_hash_for_block&#34; invoked correction recursively, it would overwrite partially filled fio-&gt;bufs.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-verity: disable recursive forward error correction</p> <p>There are two problems with the recursive correction:</p> <p>1. It may cause denial-of-service. In fec_read_bufs, there is a loop that has 253 iterations. For each iteration, we may call verity_hash_for_block recursively. There is a limit of 4 nested recursions - that means that there may be at most 253^4 (4 billion) iterations. Red Hat QE team actually created an image that pushes dm-verity to this limit - and this image just makes the udev-worker process get stuck in the &#39;D&#39; state.</p> <p>2. It doesn&#39;t work. In fec_read_bufs we store data into the variable &#34;fio-&gt;bufs&#34;, but fio bufs is shared between recursive invocations, if &#34;verity_hash_for_block&#34; invoked correction recursively, it would overwrite partially filled fio-&gt;bufs.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-71161 https://cve.radiocsirt.org/vuln/ghsa-m3cp-9jq6-3gg3 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-verity: disable recursive forward error correction</p> <p>There are two problems with the recursive correction:</p> <p>1. It may cause denial-of-service. In fec_read_bufs, there is a loop that has 253 iterations. For each iteration, we may call verity_hash_for_block recursively. There is a limit of 4 nested recursions - that means that there may be at most 253^4 (4 billion) iterations. Red Hat QE team actually created an image that pushes dm-verity to this limit - and this image just makes the udev-worker process get stuck in the &#39;D&#39; state.</p> <p>2. It doesn&#39;t work. In fec_read_bufs we store data into the variable &#34;fio-&gt;bufs&#34;, but fio bufs is shared between recursive invocations, if &#34;verity_hash_for_block&#34; invoked correction recursively, it would overwrite partially filled fio-&gt;bufs.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dm-verity: disable recursive forward error correction</p> <p>There are two problems with the recursive correction:</p> <p>1. It may cause denial-of-service. In fec_read_bufs, there is a loop that has 253 iterations. For each iteration, we may call verity_hash_for_block recursively. There is a limit of 4 nested recursions - that means that there may be at most 253^4 (4 billion) iterations. Red Hat QE team actually created an image that pushes dm-verity to this limit - and this image just makes the udev-worker process get stuck in the &#39;D&#39; state.</p> <p>2. It doesn&#39;t work. In fec_read_bufs we store data into the variable &#34;fio-&gt;bufs&#34;, but fio bufs is shared between recursive invocations, if &#34;verity_hash_for_block&#34; invoked correction recursively, it would overwrite partially filled fio-&gt;bufs.</p> https://cve.radiocsirt.org/vuln/ghsa-m3cp-9jq6-3gg3 https://cve.radiocsirt.org/vuln/icsa-26-209-04 <p>Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).</p> <p>Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.</p> <p>Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).</p> <p>Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.</p> https://cve.radiocsirt.org/vuln/icsa-26-209-04 https://cve.radiocsirt.org/vuln/msrc_cve-2025-71161 msrc_CVE-2025-71161 https://cve.radiocsirt.org/vuln/msrc_cve-2025-71161 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-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:20416-1 https://cve.radiocsirt.org/vuln/ssa-019113 <p>Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).</p> <p>Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.</p> <p>Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).</p> <p>Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.</p> https://cve.radiocsirt.org/vuln/ssa-019113 https://cve.radiocsirt.org/vuln/suse-su-2026:20838-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:20838-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71161 <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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dm-verity: disable recursive forward error correction There are two problems with the recursive correction: 1. It may cause denial-of-service. In fec_read_bufs, there is a loop that has 253 iterations. For each iteration, we may call verity_hash_for_block recursively. There is a limit of 4 nested recursions - that means that there may be at most 253^4 (4 billion) iterations. Red Hat QE team actually created an image that pushes dm-verity to this limit - and this image just makes the udev-worker process get stuck in the &#39;D&#39; state. 2. It doesn&#39;t work. In fec_read_bufs we store data into the variable &#34;fio-&gt;bufs&#34;, but fio bufs is shared between recursive invocations, if &#34;verity_hash_for_block&#34; invoked correction recursively, it would overwrite partially filled fio-&gt;bufs.</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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dm-verity: disable recursive forward error correction There are two problems with the recursive correction: 1. It may cause denial-of-service. In fec_read_bufs, there is a loop that has 253 iterations. For each iteration, we may call verity_hash_for_block recursively. There is a limit of 4 nested recursions - that means that there may be at most 253^4 (4 billion) iterations. Red Hat QE team actually created an image that pushes dm-verity to this limit - and this image just makes the udev-worker process get stuck in the &#39;D&#39; state. 2. It doesn&#39;t work. In fec_read_bufs we store data into the variable &#34;fio-&gt;bufs&#34;, but fio bufs is shared between recursive invocations, if &#34;verity_hash_for_block&#34; invoked correction recursively, it would overwrite partially filled fio-&gt;bufs.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71161 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0215 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0215