https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 18:28:33 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-14276 bdu:2026-14276 https://cve.radiocsirt.org/vuln/bdu:2026-14276 https://cve.radiocsirt.org/vuln/bell-cve-2026-64120 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-64120 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-338759 EUVD-2026-338759 https://cve.radiocsirt.org/vuln/euvd-2026-338759 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64120 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: ethtool: fix NULL pointer dereference in phy_reply_size</p> <p>In phy_prepare_data(), several strings such as &#39;name&#39;, &#39;drvname&#39;, &#39;upstream_sfp_name&#39;, and &#39;downstream_sfp_name&#39; are allocated using kstrdup(). However, these allocations were not checked for failure.</p> <p>If kstrdup() fails for &#39;name&#39;, it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer.</p> <p>While other strings like &#39;upstream_sfp_name&#39; might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs.</p> <p>Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: ethtool: fix NULL pointer dereference in phy_reply_size</p> <p>In phy_prepare_data(), several strings such as &#39;name&#39;, &#39;drvname&#39;, &#39;upstream_sfp_name&#39;, and &#39;downstream_sfp_name&#39; are allocated using kstrdup(). However, these allocations were not checked for failure.</p> <p>If kstrdup() fails for &#39;name&#39;, it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer.</p> <p>While other strings like &#39;upstream_sfp_name&#39; might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs.</p> <p>Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-64120 https://cve.radiocsirt.org/vuln/ghsa-4j8v-vv2j-8xpv <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: ethtool: fix NULL pointer dereference in phy_reply_size</p> <p>In phy_prepare_data(), several strings such as &#39;name&#39;, &#39;drvname&#39;, &#39;upstream_sfp_name&#39;, and &#39;downstream_sfp_name&#39; are allocated using kstrdup(). However, these allocations were not checked for failure.</p> <p>If kstrdup() fails for &#39;name&#39;, it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer.</p> <p>While other strings like &#39;upstream_sfp_name&#39; might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs.</p> <p>Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: ethtool: fix NULL pointer dereference in phy_reply_size</p> <p>In phy_prepare_data(), several strings such as &#39;name&#39;, &#39;drvname&#39;, &#39;upstream_sfp_name&#39;, and &#39;downstream_sfp_name&#39; are allocated using kstrdup(). However, these allocations were not checked for failure.</p> <p>If kstrdup() fails for &#39;name&#39;, it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer.</p> <p>While other strings like &#39;upstream_sfp_name&#39; might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs.</p> <p>Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.</p> https://cve.radiocsirt.org/vuln/ghsa-4j8v-vv2j-8xpv https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64120 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: ethtool: fix NULL pointer dereference in phy_reply_size In phy_prepare_data(), several strings such as &#39;name&#39;, &#39;drvname&#39;, &#39;upstream_sfp_name&#39;, and &#39;downstream_sfp_name&#39; are allocated using kstrdup(). However, these allocations were not checked for failure. If kstrdup() fails for &#39;name&#39;, it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer. While other strings like &#39;upstream_sfp_name&#39; might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs. Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: ethtool: fix NULL pointer dereference in phy_reply_size In phy_prepare_data(), several strings such as &#39;name&#39;, &#39;drvname&#39;, &#39;upstream_sfp_name&#39;, and &#39;downstream_sfp_name&#39; are allocated using kstrdup(). However, these allocations were not checked for failure. If kstrdup() fails for &#39;name&#39;, it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer. While other strings like &#39;upstream_sfp_name&#39; might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs. Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64120 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403