<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T03:28:49.919187+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-53232</id>
    <title>BELL-CVE-2026-53232</title>
    <updated>2026-10-03T03:28:49.934513+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-53232"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162</id>
    <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>
    <updated>2026-10-03T03:28:49.934567+00:00</updated>
    <content>certfr-2026-avi-1162</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-348209</id>
    <title>EUVD-2026-348209</title>
    <updated>2026-10-03T03:28:49.934587+00:00</updated>
    <content>EUVD-2026-348209</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-348209"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53232</id>
    <title>fkie_cve-2026-53232</title>
    <updated>2026-10-03T03:28:49.934599+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: phy: clean the sfp upstream if phy probing fails</p>
<p>Sashiko reported that we don't call sfp_bus_del_upstream() in the probe
failure path, so let's add it, otherwise the sfp-bus is left with a
dangling 'upstream' field, that may be used later on during SFP events.</p>
<p>This issue existed before the generic phylib sfp support, back when
drivers were calling phy_sfp_probe themselves.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-53232"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-grrc-m4h5-r55j</id>
    <title>GHSA-grrc-m4h5-r55j</title>
    <updated>2026-10-03T03:28:49.934627+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: phy: clean the sfp upstream if phy probing fails</p>
<p>Sashiko reported that we don't call sfp_bus_del_upstream() in the probe
failure path, so let's add it, otherwise the sfp-bus is left with a
dangling 'upstream' field, that may be used later on during SFP events.</p>
<p>This issue existed before the generic phylib sfp support, back when
drivers were calling phy_sfp_probe themselves.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-grrc-m4h5-r55j"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53232</id>
    <title>msrc_CVE-2026-53232 — net: phy: clean the sfp upstream if phy probing fails</title>
    <updated>2026-10-03T03:28:49.934646+00:00</updated>
    <content>msrc_CVE-2026-53232</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-53232"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-3206</id>
    <title>OESA-2026-3206 — kernel security update</title>
    <updated>2026-10-03T03:28:49.934661+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>Arm C1-Ultra, C1-Premium, Neoverse V3 &amp;amp; V3AE, Neoverse V2, Neoverse V1, Neoverse-N2, Neoverse-N1, Cortex-X925, Cortex-X4, Cortex-X3, Cortex-X2, Cortex-X1 &amp;amp; X1C, Cortex-A710, Cortex-A78, A78AE &amp;amp; A78C, Cortex-A77, Cortex-A76 &amp;amp; A76A may allow writes to resources owned by a higher exception level.(CVE-2025-10263)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP</p>
<p>Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.</p>
<p>socket(AF_INET, SOCK_RAW, 255);</p>
<p>A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.</p>
<p>inner = IP(src=&amp;quot;192.168.2.1&amp;quot;, dst=&amp;quot;8.8.8.8&amp;quot;, proto=255)/Raw(&amp;quot;TEST&amp;quot;)
pkt = IP(src=&amp;quot;192.168.1.1&amp;quot;, dst=&amp;quot;192.168.2.1&amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner</p>
<p>&amp;quot;man 7 raw&amp;quot; states:</p>
<p>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.</p>
<p>Make sure we drop these malicious packets.(CVE-2026-46266)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tun: free page on build_skb failure in tun_xdp_one()</p>
<p>When build_skb() fails in tun_xdp_one(), the function sets ret to
-…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-3206"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53232</id>
    <title>UBUNTU-CVE-2026-53232</title>
    <updated>2026-10-03T03:28:49.934782+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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 202 more</p>
<p>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't call sfp_bus_del_upstream() in the probe failure path, so let's add it, otherwise the sfp-bus is left with a dangling 'upstream' 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53232"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</id>
    <title>WID-SEC-W-2026-2077 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T03:28:49.935006+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <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>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077"/>
  </entry>
</feed>
