<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 03:27:59 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53232</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53232</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-53232</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1162 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162</link>
      <description>certfr-2026-avi-1162</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162</guid>
    </item>
    <item>
      <title>EUVD-2026-348209</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348209</link>
      <description>EUVD-2026-348209</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348209</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53232</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53232</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: phy: clean the sfp upstream if phy probing fails&lt;/p&gt;
&lt;p&gt;Sashiko reported that we don&amp;#39;t call sfp_bus_del_upstream() in the probe
failure path, so let&amp;#39;s add it, otherwise the sfp-bus is left with a
dangling &amp;#39;upstream&amp;#39; field, that may be used later on during SFP events.&lt;/p&gt;
&lt;p&gt;This issue existed before the generic phylib sfp support, back when
drivers were calling phy_sfp_probe themselves.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: phy: clean the sfp upstream if phy probing fails&lt;/p&gt;
&lt;p&gt;Sashiko reported that we don&amp;#39;t call sfp_bus_del_upstream() in the probe
failure path, so let&amp;#39;s add it, otherwise the sfp-bus is left with a
dangling &amp;#39;upstream&amp;#39; field, that may be used later on during SFP events.&lt;/p&gt;
&lt;p&gt;This issue existed before the generic phylib sfp support, back when
drivers were calling phy_sfp_probe themselves.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53232</guid>
    </item>
    <item>
      <title>GHSA-grrc-m4h5-r55j</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-grrc-m4h5-r55j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: phy: clean the sfp upstream if phy probing fails&lt;/p&gt;
&lt;p&gt;Sashiko reported that we don&amp;#39;t call sfp_bus_del_upstream() in the probe
failure path, so let&amp;#39;s add it, otherwise the sfp-bus is left with a
dangling &amp;#39;upstream&amp;#39; field, that may be used later on during SFP events.&lt;/p&gt;
&lt;p&gt;This issue existed before the generic phylib sfp support, back when
drivers were calling phy_sfp_probe themselves.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: phy: clean the sfp upstream if phy probing fails&lt;/p&gt;
&lt;p&gt;Sashiko reported that we don&amp;#39;t call sfp_bus_del_upstream() in the probe
failure path, so let&amp;#39;s add it, otherwise the sfp-bus is left with a
dangling &amp;#39;upstream&amp;#39; field, that may be used later on during SFP events.&lt;/p&gt;
&lt;p&gt;This issue existed before the generic phylib sfp support, back when
drivers were calling phy_sfp_probe themselves.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-grrc-m4h5-r55j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-53232 — net: phy: clean the sfp upstream if phy probing fails</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53232</link>
      <description>msrc_CVE-2026-53232</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-53232</guid>
    </item>
    <item>
      <title>OESA-2026-3206 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3206</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;Arm C1-Ultra, C1-Premium, Neoverse V3 &amp;amp;amp; V3AE, Neoverse V2, Neoverse V1, Neoverse-N2, Neoverse-N1, Cortex-X925, Cortex-X4, Cortex-X3, Cortex-X2, Cortex-X1 &amp;amp;amp; X1C, Cortex-A710, Cortex-A78, A78AE &amp;amp;amp; A78C, Cortex-A77, Cortex-A76 &amp;amp;amp; A76A may allow writes to resources owned by a higher exception level.(CVE-2025-10263)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP&lt;/p&gt;
&lt;p&gt;Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.&lt;/p&gt;
&lt;p&gt;socket(AF_INET, SOCK_RAW, 255);&lt;/p&gt;
&lt;p&gt;A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.&lt;/p&gt;
&lt;p&gt;inner = IP(src=&amp;amp;quot;192.168.2.1&amp;amp;quot;, dst=&amp;amp;quot;8.8.8.8&amp;amp;quot;, proto=255)/Raw(&amp;amp;quot;TEST&amp;amp;quot;)
pkt = IP(src=&amp;amp;quot;192.168.1.1&amp;amp;quot;, dst=&amp;amp;quot;192.168.2.1&amp;amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;man 7 raw&amp;amp;quot; states:&lt;/p&gt;
&lt;p&gt;A protocol of IPPROTO_RAW implies enabled IP_HDRINCL and is able
  to send any IP protocol that is specified in the passed header.
  Receiving of all IP protocols via IPPROTO_RAW is not possible
  using raw sockets.&lt;/p&gt;
&lt;p&gt;Make sure we drop these malicious packets.(CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tun: free page on build_skb failure in tun_xdp_one()&lt;/p&gt;
&lt;p&gt;When build_skb() fails in tun_xdp_one(), the function sets ret to
-…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;Arm C1-Ultra, C1-Premium, Neoverse V3 &amp;amp;amp; V3AE, Neoverse V2, Neoverse V1, Neoverse-N2, Neoverse-N1, Cortex-X925, Cortex-X4, Cortex-X3, Cortex-X2, Cortex-X1 &amp;amp;amp; X1C, Cortex-A710, Cortex-A78, A78AE &amp;amp;amp; A78C, Cortex-A77, Cortex-A76 &amp;amp;amp; A76A may allow writes to resources owned by a higher exception level.(CVE-2025-10263)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP&lt;/p&gt;
&lt;p&gt;Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.&lt;/p&gt;
&lt;p&gt;socket(AF_INET, SOCK_RAW, 255);&lt;/p&gt;
&lt;p&gt;A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.&lt;/p&gt;
&lt;p&gt;inner = IP(src=&amp;amp;quot;192.168.2.1&amp;amp;quot;, dst=&amp;amp;quot;8.8.8.8&amp;amp;quot;, proto=255)/Raw(&amp;amp;quot;TEST&amp;amp;quot;)
pkt = IP(src=&amp;amp;quot;192.168.1.1&amp;amp;quot;, dst=&amp;amp;quot;192.168.2.1&amp;amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;man 7 raw&amp;amp;quot; states:&lt;/p&gt;
&lt;p&gt;A protocol of IPPROTO_RAW implies enabled IP_HDRINCL and is able
  to send any IP protocol that is specified in the passed header.
  Receiving of all IP protocols via IPPROTO_RAW is not possible
  using raw sockets.&lt;/p&gt;
&lt;p&gt;Make sure we drop these malicious packets.(CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tun: free page on build_skb failure in tun_xdp_one()&lt;/p&gt;
&lt;p&gt;When build_skb() fails in tun_xdp_one(), the function sets ret to
-…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3206</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53232</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53232</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 202 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: phy: clean the sfp upstream if phy probing fails Sashiko reported that we don&amp;#39;t call sfp_bus_del_upstream() in the probe failure path, so let&amp;#39;s add it, otherwise the sfp-bus is left with a dangling &amp;#39;upstream&amp;#39; field, that may be used later on during SFP events. This issue existed before the generic phylib sfp support, back when drivers were calling phy_sfp_probe themselves.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 202 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: phy: clean the sfp upstream if phy probing fails Sashiko reported that we don&amp;#39;t call sfp_bus_del_upstream() in the probe failure path, so let&amp;#39;s add it, otherwise the sfp-bus is left with a dangling &amp;#39;upstream&amp;#39; field, that may be used later on during SFP events. This issue existed before the generic phylib sfp support, back when drivers were calling phy_sfp_probe themselves.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53232</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2077 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</guid>
    </item>
  </channel>
</rss>
