https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:16:44 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-01352 bdu:2026-01352 https://cve.radiocsirt.org/vuln/bdu:2026-01352 https://cve.radiocsirt.org/vuln/bell-cve-2025-40337 <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-40337 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-347434 EUVD-2026-347434 https://cve.radiocsirt.org/vuln/euvd-2026-347434 https://cve.radiocsirt.org/vuln/fkie_cve-2025-40337 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stmmac: Correctly handle Rx checksum offload errors</p> <p>The stmmac_rx function would previously set skb-&gt;ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a known IP ethertype.</p> <p>However, this logic failed to check if the hardware had actually reported a checksum error. The hardware status, indicating a header or payload checksum failure, was being ignored at this stage. This could cause corrupt packets to be passed up the network stack as valid.</p> <p>This patch corrects the logic by checking the `csum_none` status flag, which is set when the hardware reports a checksum error. If this flag is set, skb-&gt;ip_summed is now correctly set to CHECKSUM_NONE, ensuring the kernel&#39;s network stack will perform its own validation and properly handle the corrupt packet.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stmmac: Correctly handle Rx checksum offload errors</p> <p>The stmmac_rx function would previously set skb-&gt;ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a known IP ethertype.</p> <p>However, this logic failed to check if the hardware had actually reported a checksum error. The hardware status, indicating a header or payload checksum failure, was being ignored at this stage. This could cause corrupt packets to be passed up the network stack as valid.</p> <p>This patch corrects the logic by checking the `csum_none` status flag, which is set when the hardware reports a checksum error. If this flag is set, skb-&gt;ip_summed is now correctly set to CHECKSUM_NONE, ensuring the kernel&#39;s network stack will perform its own validation and properly handle the corrupt packet.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-40337 https://cve.radiocsirt.org/vuln/ghsa-4h2c-rg8h-8jqc <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stmmac: Correctly handle Rx checksum offload errors</p> <p>The stmmac_rx function would previously set skb-&gt;ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a known IP ethertype.</p> <p>However, this logic failed to check if the hardware had actually reported a checksum error. The hardware status, indicating a header or payload checksum failure, was being ignored at this stage. This could cause corrupt packets to be passed up the network stack as valid.</p> <p>This patch corrects the logic by checking the `csum_none` status flag, which is set when the hardware reports a checksum error. If this flag is set, skb-&gt;ip_summed is now correctly set to CHECKSUM_NONE, ensuring the kernel&#39;s network stack will perform its own validation and properly handle the corrupt packet.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: stmmac: Correctly handle Rx checksum offload errors</p> <p>The stmmac_rx function would previously set skb-&gt;ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a known IP ethertype.</p> <p>However, this logic failed to check if the hardware had actually reported a checksum error. The hardware status, indicating a header or payload checksum failure, was being ignored at this stage. This could cause corrupt packets to be passed up the network stack as valid.</p> <p>This patch corrects the logic by checking the `csum_none` status flag, which is set when the hardware reports a checksum error. If this flag is set, skb-&gt;ip_summed is now correctly set to CHECKSUM_NONE, ensuring the kernel&#39;s network stack will perform its own validation and properly handle the corrupt packet.</p> https://cve.radiocsirt.org/vuln/ghsa-4h2c-rg8h-8jqc https://cve.radiocsirt.org/vuln/msrc_cve-2025-40337 msrc_CVE-2025-40337 https://cve.radiocsirt.org/vuln/msrc_cve-2025-40337 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-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:20145-1 https://cve.radiocsirt.org/vuln/suse-su-2026:0278-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:0278-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40337 <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 229 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Correctly handle Rx checksum offload errors The stmmac_rx function would previously set skb-&gt;ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a known IP ethertype. However, this logic failed to check if the hardware had actually reported a checksum error. The hardware status, indicating a header or payload checksum failure, was being ignored at this stage. This could cause corrupt packets to be passed up the network stack as valid. This patch corrects the logic by checking the `csum_none` status flag, which is set when the hardware reports a checksum error. If this flag is set, skb-&gt;ip_summed is now correctly set to CHECKSUM_NONE, ensuring the kernel&#39;s network stack will perform its own validation and properly handle the corrupt packet.</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 229 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: stmmac: Correctly handle Rx checksum offload errors The stmmac_rx function would previously set skb-&gt;ip_summed to CHECKSUM_UNNECESSARY if hardware checksum offload (CoE) was enabled and the packet was of a known IP ethertype. However, this logic failed to check if the hardware had actually reported a checksum error. The hardware status, indicating a header or payload checksum failure, was being ignored at this stage. This could cause corrupt packets to be passed up the network stack as valid. This patch corrects the logic by checking the `csum_none` status flag, which is set when the hardware reports a checksum error. If this flag is set, skb-&gt;ip_summed is now correctly set to CHECKSUM_NONE, ensuring the kernel&#39;s network stack will perform its own validation and properly handle the corrupt packet.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40337 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765