<?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 04:10:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11258</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11258</link>
      <description>bdu:2026-11258</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11258</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-31504</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-31504</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-31504</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0519 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0519</link>
      <description>certfr-2026-avi-0519</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0519</guid>
    </item>
    <item>
      <title>EUVD-2026-364752</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-364752</link>
      <description>EUVD-2026-364752</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-364752</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31504</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31504</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix fanout UAF in packet_release() via NETDEV_UP race&lt;/p&gt;
&lt;p&gt;`packet_release()` has a race window where `NETDEV_UP` can re-register a
socket into a fanout group&amp;#39;s `arr[]` array. The re-registration is not
cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout
array.
`packet_release()` does NOT zero `po-&amp;gt;num` in its `bind_lock` section.
After releasing `bind_lock`, `po-&amp;gt;num` is still non-zero and `po-&amp;gt;ifindex`
still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)`
that already found the socket in `sklist` can re-register the hook.
For fanout sockets, this re-registration calls `__fanout_link(sk, po)`
which adds the socket back into `f-&amp;gt;arr[]` and increments `f-&amp;gt;num_members`,
but does NOT increment `f-&amp;gt;sk_ref`.&lt;/p&gt;
&lt;p&gt;The fix sets `po-&amp;gt;num` to zero in `packet_release` while `bind_lock` is
held to prevent NETDEV_UP from linking, preventing the race window.&lt;/p&gt;
&lt;p&gt;This bug was found following an additional audit with Claude Code based
on CVE-2025-38617.&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: fix fanout UAF in packet_release() via NETDEV_UP race&lt;/p&gt;
&lt;p&gt;`packet_release()` has a race window where `NETDEV_UP` can re-register a
socket into a fanout group&amp;#39;s `arr[]` array. The re-registration is not
cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout
array.
`packet_release()` does NOT zero `po-&amp;gt;num` in its `bind_lock` section.
After releasing `bind_lock`, `po-&amp;gt;num` is still non-zero and `po-&amp;gt;ifindex`
still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)`
that already found the socket in `sklist` can re-register the hook.
For fanout sockets, this re-registration calls `__fanout_link(sk, po)`
which adds the socket back into `f-&amp;gt;arr[]` and increments `f-&amp;gt;num_members`,
but does NOT increment `f-&amp;gt;sk_ref`.&lt;/p&gt;
&lt;p&gt;The fix sets `po-&amp;gt;num` to zero in `packet_release` while `bind_lock` is
held to prevent NETDEV_UP from linking, preventing the race window.&lt;/p&gt;
&lt;p&gt;This bug was found following an additional audit with Claude Code based
on CVE-2025-38617.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31504</guid>
    </item>
    <item>
      <title>GHSA-5v9p-3rfc-6rw2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5v9p-3rfc-6rw2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix fanout UAF in packet_release() via NETDEV_UP race&lt;/p&gt;
&lt;p&gt;`packet_release()` has a race window where `NETDEV_UP` can re-register a
socket into a fanout group&amp;#39;s `arr[]` array. The re-registration is not
cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout
array.
`packet_release()` does NOT zero `po-&amp;gt;num` in its `bind_lock` section.
After releasing `bind_lock`, `po-&amp;gt;num` is still non-zero and `po-&amp;gt;ifindex`
still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)`
that already found the socket in `sklist` can re-register the hook.
For fanout sockets, this re-registration calls `__fanout_link(sk, po)`
which adds the socket back into `f-&amp;gt;arr[]` and increments `f-&amp;gt;num_members`,
but does NOT increment `f-&amp;gt;sk_ref`.&lt;/p&gt;
&lt;p&gt;The fix sets `po-&amp;gt;num` to zero in `packet_release` while `bind_lock` is
held to prevent NETDEV_UP from linking, preventing the race window.&lt;/p&gt;
&lt;p&gt;This bug was found following an additional audit with Claude Code based
on CVE-2025-38617.&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: fix fanout UAF in packet_release() via NETDEV_UP race&lt;/p&gt;
&lt;p&gt;`packet_release()` has a race window where `NETDEV_UP` can re-register a
socket into a fanout group&amp;#39;s `arr[]` array. The re-registration is not
cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout
array.
`packet_release()` does NOT zero `po-&amp;gt;num` in its `bind_lock` section.
After releasing `bind_lock`, `po-&amp;gt;num` is still non-zero and `po-&amp;gt;ifindex`
still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)`
that already found the socket in `sklist` can re-register the hook.
For fanout sockets, this re-registration calls `__fanout_link(sk, po)`
which adds the socket back into `f-&amp;gt;arr[]` and increments `f-&amp;gt;num_members`,
but does NOT increment `f-&amp;gt;sk_ref`.&lt;/p&gt;
&lt;p&gt;The fix sets `po-&amp;gt;num` to zero in `packet_release` while `bind_lock` is
held to prevent NETDEV_UP from linking, preventing the race window.&lt;/p&gt;
&lt;p&gt;This bug was found following an additional audit with Claude Code based
on CVE-2025-38617.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5v9p-3rfc-6rw2</guid>
    </item>
    <item>
      <title>ICSA-26-209-04 — Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-26-209-04</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens is preparing fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-26-209-04</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-31504 — net: fix fanout UAF in packet_release() via NETDEV_UP race</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-31504</link>
      <description>msrc_CVE-2026-31504</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-31504</guid>
    </item>
    <item>
      <title>OESA-2026-2310 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2310</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix fanout UAF in packet_release() via NETDEV_UP race&lt;/p&gt;
&lt;p&gt;`packet_release()` has a race window where `NETDEV_UP` can re-register a
socket into a fanout group&amp;amp;apos;s `arr[]` array. The re-registration is not
cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout
array.
`packet_release()` does NOT zero `po-&amp;amp;gt;num` in its `bind_lock` section.
After releasing `bind_lock`, `po-&amp;amp;gt;num` is still non-zero and `po-&amp;amp;gt;ifindex`
still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)`
that already found the socket in `sklist` can re-register the hook.
For fanout sockets, this re-registration calls `__fanout_link(sk, po)`
which adds the socket back into `f-&amp;amp;gt;arr[]` and increments `f-&amp;amp;gt;num_members`,
but does NOT increment `f-&amp;amp;gt;sk_ref`.&lt;/p&gt;
&lt;p&gt;The fix sets `po-&amp;amp;gt;num` to zero in `packet_release` while `bind_lock` is
held to prevent NETDEV_UP from linking, preventing the race window.&lt;/p&gt;
&lt;p&gt;This bug was found following an additional audit with Claude Code based
on CVE-2025-38617.(CVE-2026-31504)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;af_key: validate families in pfkey_send_migrate()&lt;/p&gt;
&lt;p&gt;syzbot was able to trigger a crash in skb_put() [1]&lt;/p&gt;
&lt;p&gt;Issue is that pfkey_send_migrate() does not check old/new families,
and that set_ipsecrequest() @family argument was truncated,
thus possibly overfill…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix fanout UAF in packet_release() via NETDEV_UP race&lt;/p&gt;
&lt;p&gt;`packet_release()` has a race window where `NETDEV_UP` can re-register a
socket into a fanout group&amp;amp;apos;s `arr[]` array. The re-registration is not
cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout
array.
`packet_release()` does NOT zero `po-&amp;amp;gt;num` in its `bind_lock` section.
After releasing `bind_lock`, `po-&amp;amp;gt;num` is still non-zero and `po-&amp;amp;gt;ifindex`
still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)`
that already found the socket in `sklist` can re-register the hook.
For fanout sockets, this re-registration calls `__fanout_link(sk, po)`
which adds the socket back into `f-&amp;amp;gt;arr[]` and increments `f-&amp;amp;gt;num_members`,
but does NOT increment `f-&amp;amp;gt;sk_ref`.&lt;/p&gt;
&lt;p&gt;The fix sets `po-&amp;amp;gt;num` to zero in `packet_release` while `bind_lock` is
held to prevent NETDEV_UP from linking, preventing the race window.&lt;/p&gt;
&lt;p&gt;This bug was found following an additional audit with Claude Code based
on CVE-2025-38617.(CVE-2026-31504)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;af_key: validate families in pfkey_send_migrate()&lt;/p&gt;
&lt;p&gt;syzbot was able to trigger a crash in skb_put() [1]&lt;/p&gt;
&lt;p&gt;Issue is that pfkey_send_migrate() does not check old/new families,
and that set_ipsecrequest() @family argument was truncated,
thus possibly overfill…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2310</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20826-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1</guid>
    </item>
    <item>
      <title>SSA-019113 — SSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-019113</link>
      <description>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Multiple vulnerabilities have been identified in the additional GNU/Linux subsystem of the firmware version V3.1.6 for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP (incl. SIPLUS variant).&lt;/p&gt;
&lt;p&gt;Siemens has released new versions for several affected products and recommends to update to the latest versions. Siemens is preparing further fix versions and recommends specific countermeasures for products where fixes are not, or not yet available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-019113</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:2068-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:2068-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:2068-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31504</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31504</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-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-kvm and 230 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: fix fanout UAF in packet_release() via NETDEV_UP race `packet_release()` has a race window where `NETDEV_UP` can re-register a socket into a fanout group&amp;#39;s `arr[]` array. The re-registration is not cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout array. `packet_release()` does NOT zero `po-&amp;gt;num` in its `bind_lock` section. After releasing `bind_lock`, `po-&amp;gt;num` is still non-zero and `po-&amp;gt;ifindex` still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)` that already found the socket in `sklist` can re-register the hook. For fanout sockets, this re-registration calls `__fanout_link(sk, po)` which adds the socket back into `f-&amp;gt;arr[]` and increments `f-&amp;gt;num_members`, but does NOT increment `f-&amp;gt;sk_ref`. The fix sets `po-&amp;gt;num` to zero in `packet_release` while `bind_lock` is held to prevent NETDEV_UP from linking, preventing the race window. This bug was found following an additional audit with Claude Code based on CVE-2025-38617.&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-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-kvm and 230 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: fix fanout UAF in packet_release() via NETDEV_UP race `packet_release()` has a race window where `NETDEV_UP` can re-register a socket into a fanout group&amp;#39;s `arr[]` array. The re-registration is not cleaned up by `fanout_release()`, leaving a dangling pointer in the fanout array. `packet_release()` does NOT zero `po-&amp;gt;num` in its `bind_lock` section. After releasing `bind_lock`, `po-&amp;gt;num` is still non-zero and `po-&amp;gt;ifindex` still matches the bound device. A concurrent `packet_notifier(NETDEV_UP)` that already found the socket in `sklist` can re-register the hook. For fanout sockets, this re-registration calls `__fanout_link(sk, po)` which adds the socket back into `f-&amp;gt;arr[]` and increments `f-&amp;gt;num_members`, but does NOT increment `f-&amp;gt;sk_ref`. The fix sets `po-&amp;gt;num` to zero in `packet_release` while `bind_lock` is held to prevent NETDEV_UP from linking, preventing the race window. This bug was found following an additional audit with Claude Code based on CVE-2025-38617.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31504</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1252 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1252</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1252</guid>
    </item>
  </channel>
</rss>
