<?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-03T06:01:58.202534+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/bdu:2025-12038</id>
    <title>bdu:2025-12038</title>
    <updated>2026-10-03T06:01:58.225591+00:00</updated>
    <content>bdu:2025-12038</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-12038"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2025-22073</id>
    <title>BELL-CVE-2025-22073</title>
    <updated>2026-10-03T06:01:58.225629+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-2025-22073"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0368</id>
    <title>certfr-2025-avi-0368 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-10-03T06:01:58.225659+00:00</updated>
    <content>certfr-2025-avi-0368</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2025-avi-0368"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-314170</id>
    <title>EUVD-2026-314170</title>
    <updated>2026-10-03T06:01:58.225676+00:00</updated>
    <content>EUVD-2026-314170</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-314170"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-22073</id>
    <title>fkie_cve-2025-22073</title>
    <updated>2026-10-03T06:01:58.225687+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>spufs: fix a leak on spufs_new_file() failure</p>
<p>It's called from spufs_fill_dir(), and caller of that will do
spufs_rmdir() in case of failure.  That does remove everything
we'd managed to create, but... the problem dentry is still
negative.  IOW, it needs to be explicitly dropped.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-22073"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-92m7-rr4r-78cq</id>
    <title>GHSA-92m7-rr4r-78cq</title>
    <updated>2026-10-03T06:01:58.225714+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>spufs: fix a leak on spufs_new_file() failure</p>
<p>It's called from spufs_fill_dir(), and caller of that will do
spufs_rmdir() in case of failure.  That does remove everything
we'd managed to create, but... the problem dentry is still
negative.  IOW, it needs to be explicitly dropped.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-92m7-rr4r-78cq"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-22073</id>
    <title>msrc_CVE-2025-22073 — spufs: fix a leak on spufs_new_file() failure</title>
    <updated>2026-10-03T06:01:58.225731+00:00</updated>
    <content>msrc_CVE-2025-22073</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-22073"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2025-2407</id>
    <title>OESA-2025-2407 — kernel security update</title>
    <updated>2026-10-03T06:01:58.225746+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP3: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: dsa: Avoid cross-chip syncing of VLAN filtering</p>
<p>Changes to VLAN filtering are not applicable to cross-chip
notifications.</p>
<p>On a system like this:</p>
<p>.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;apos;-1-2-&amp;apos;   &amp;apos;-1-2-&amp;apos;   &amp;apos;-1-2-&amp;apos;</p>
<p>Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.</p>
<p>In this scenario:</p>
<p>.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;apos;-1-2-3-4-&amp;apos;   &amp;apos;-1-2-&amp;apos;   &amp;apos;-1-2-&amp;apos;</p>
<p>When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be
called for sw2 and sw3 with a non-existing port - leading to array
out-of-bounds accesses and crashes on mv88e6xxx.(CVE-2022-49234)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: target: iscsi: Fix a race condition between login_work and the login thread</p>
<p>In case a malicious initiator sends some random data immediately after a
login PDU; the iscsi_target_sk_data_ready() callback will schedule the
login_work and, at the same time, the negotiation may end without clearing
the LOGIN_FLAGS_INITIAL_PDU flag (because no additional PDU exchanges are
required to complete the login).</p>
<p>The login has been completed but the login_work function will find the
LOGIN_FLAGS_INITIAL_PDU flag set and will never stop from rescheduling…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2025-2407"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22073</id>
    <title>UBUNTU-CVE-2025-22073</title>
    <updated>2026-10-03T06:01:58.225875+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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 203 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: spufs: fix a leak on spufs_new_file() failure It's called from spufs_fill_dir(), and caller of that will do spufs_rmdir() in case of failure.  That does remove everything we'd managed to create, but... the problem dentry is still negative.  IOW, it needs to be explicitly dropped.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22073"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</id>
    <title>WID-SEC-W-2025-0844 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T06:01:58.226109+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844"/>
  </entry>
</feed>
