<?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 06:01:51 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12038</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12038</link>
      <description>bdu:2025-12038</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12038</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-22073</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-22073</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-2025-22073</guid>
    </item>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0368</link>
      <description>certfr-2025-avi-0368</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0368</guid>
    </item>
    <item>
      <title>EUVD-2026-314170</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314170</link>
      <description>EUVD-2026-314170</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314170</guid>
    </item>
    <item>
      <title>fkie_cve-2025-22073</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-22073</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;spufs: fix a leak on spufs_new_file() failure&lt;/p&gt;
&lt;p&gt;It&amp;#39;s called from spufs_fill_dir(), and caller of that will do
spufs_rmdir() in case of failure.  That does remove everything
we&amp;#39;d managed to create, but... the problem dentry is still
negative.  IOW, it needs to be explicitly dropped.&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;spufs: fix a leak on spufs_new_file() failure&lt;/p&gt;
&lt;p&gt;It&amp;#39;s called from spufs_fill_dir(), and caller of that will do
spufs_rmdir() in case of failure.  That does remove everything
we&amp;#39;d managed to create, but... the problem dentry is still
negative.  IOW, it needs to be explicitly dropped.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-22073</guid>
    </item>
    <item>
      <title>GHSA-92m7-rr4r-78cq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-92m7-rr4r-78cq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;spufs: fix a leak on spufs_new_file() failure&lt;/p&gt;
&lt;p&gt;It&amp;#39;s called from spufs_fill_dir(), and caller of that will do
spufs_rmdir() in case of failure.  That does remove everything
we&amp;#39;d managed to create, but... the problem dentry is still
negative.  IOW, it needs to be explicitly dropped.&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;spufs: fix a leak on spufs_new_file() failure&lt;/p&gt;
&lt;p&gt;It&amp;#39;s called from spufs_fill_dir(), and caller of that will do
spufs_rmdir() in case of failure.  That does remove everything
we&amp;#39;d managed to create, but... the problem dentry is still
negative.  IOW, it needs to be explicitly dropped.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-92m7-rr4r-78cq</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-22073 — spufs: fix a leak on spufs_new_file() failure</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-22073</link>
      <description>msrc_CVE-2025-22073</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-22073</guid>
    </item>
    <item>
      <title>OESA-2025-2407 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2407</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: dsa: Avoid cross-chip syncing of VLAN filtering&lt;/p&gt;
&lt;p&gt;Changes to VLAN filtering are not applicable to cross-chip
notifications.&lt;/p&gt;
&lt;p&gt;On a system like this:&lt;/p&gt;
&lt;p&gt;.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.&lt;/p&gt;
&lt;p&gt;In this scenario:&lt;/p&gt;
&lt;p&gt;.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-3-4-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: iscsi: Fix a race condition between login_work and the login thread&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: dsa: Avoid cross-chip syncing of VLAN filtering&lt;/p&gt;
&lt;p&gt;Changes to VLAN filtering are not applicable to cross-chip
notifications.&lt;/p&gt;
&lt;p&gt;On a system like this:&lt;/p&gt;
&lt;p&gt;.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.&lt;/p&gt;
&lt;p&gt;In this scenario:&lt;/p&gt;
&lt;p&gt;.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-3-4-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: iscsi: Fix a race condition between login_work and the login thread&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2407</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-22073</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22073</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: spufs: fix a leak on spufs_new_file() failure It&amp;#39;s called from spufs_fill_dir(), and caller of that will do spufs_rmdir() in case of failure.  That does remove everything we&amp;#39;d managed to create, but... the problem dentry is still negative.  IOW, it needs to be explicitly dropped.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: spufs: fix a leak on spufs_new_file() failure It&amp;#39;s called from spufs_fill_dir(), and caller of that will do spufs_rmdir() in case of failure.  That does remove everything we&amp;#39;d managed to create, but... the problem dentry is still negative.  IOW, it needs to be explicitly dropped.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-22073</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0844 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht genauer beschriebene Auswirkungen erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0844</guid>
    </item>
  </channel>
</rss>
