<?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 01:18:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05768</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05768</link>
      <description>bdu:2026-05768</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05768</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-31399</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-31399</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-31399</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0547 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0547</link>
      <description>certfr-2026-avi-0547</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0547</guid>
    </item>
    <item>
      <title>EUVD-2026-320961</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320961</link>
      <description>EUVD-2026-320961</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320961</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31399</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31399</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvdimm/bus: Fix potential use after free in asynchronous initialization&lt;/p&gt;
&lt;p&gt;Dingisoul with KASAN reports a use after free if device_add() fails in
nd_async_device_register().&lt;/p&gt;
&lt;p&gt;Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while
scheduling async init&amp;#34;) correctly added a reference on the parent device
to be held until asynchronous initialization was complete.  However, if
device_add() results in an allocation failure the ref count of the
device drops to 0 prior to the parent pointer being accessed.  Thus
resulting in use after free.&lt;/p&gt;
&lt;p&gt;The bug bot AI correctly identified the fix.  Save a reference to the
parent pointer to be used to drop the parent reference regardless of the
outcome of device_add().&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;nvdimm/bus: Fix potential use after free in asynchronous initialization&lt;/p&gt;
&lt;p&gt;Dingisoul with KASAN reports a use after free if device_add() fails in
nd_async_device_register().&lt;/p&gt;
&lt;p&gt;Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while
scheduling async init&amp;#34;) correctly added a reference on the parent device
to be held until asynchronous initialization was complete.  However, if
device_add() results in an allocation failure the ref count of the
device drops to 0 prior to the parent pointer being accessed.  Thus
resulting in use after free.&lt;/p&gt;
&lt;p&gt;The bug bot AI correctly identified the fix.  Save a reference to the
parent pointer to be used to drop the parent reference regardless of the
outcome of device_add().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31399</guid>
    </item>
    <item>
      <title>GHSA-j3fg-h3r6-7945</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j3fg-h3r6-7945</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvdimm/bus: Fix potential use after free in asynchronous initialization&lt;/p&gt;
&lt;p&gt;Dingisoul with KASAN reports a use after free if device_add() fails in
nd_async_device_register().&lt;/p&gt;
&lt;p&gt;Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while
scheduling async init&amp;#34;) correctly added a reference on the parent device
to be held until asynchronous initialization was complete.  However, if
device_add() results in an allocation failure the ref count of the
device drops to 0 prior to the parent pointer being accessed.  Thus
resulting in use after free.&lt;/p&gt;
&lt;p&gt;The bug bot AI correctly identified the fix.  Save a reference to the
parent pointer to be used to drop the parent reference regardless of the
outcome of device_add().&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;nvdimm/bus: Fix potential use after free in asynchronous initialization&lt;/p&gt;
&lt;p&gt;Dingisoul with KASAN reports a use after free if device_add() fails in
nd_async_device_register().&lt;/p&gt;
&lt;p&gt;Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while
scheduling async init&amp;#34;) correctly added a reference on the parent device
to be held until asynchronous initialization was complete.  However, if
device_add() results in an allocation failure the ref count of the
device drops to 0 prior to the parent pointer being accessed.  Thus
resulting in use after free.&lt;/p&gt;
&lt;p&gt;The bug bot AI correctly identified the fix.  Save a reference to the
parent pointer to be used to drop the parent reference regardless of the
outcome of device_add().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j3fg-h3r6-7945</guid>
    </item>
    <item>
      <title>OESA-2026-1946 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1946</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;mptcp: Initialise rcv_mss before calling tcp_send_active_reset() in mptcp_do_fastclose().&lt;/p&gt;
&lt;p&gt;syzbot reported divide-by-zero in __tcp_select_window() by
MPTCP socket. [0]&lt;/p&gt;
&lt;p&gt;We had a similar issue for the bare TCP and fixed in commit
499350a5a6e7 (&amp;amp;quot;tcp: initialize rcv_mss to TCP_MIN_MSS instead
of 0&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s apply the same fix to mptcp_do_fastclose().&lt;/p&gt;
&lt;p&gt;[0]:
Oops: divide error: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6068 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__tcp_select_window+0x824/0x1320 net/ipv4/tcp_output.c:3336
Code: ff ff ff 44 89 f1 d3 e0 89 c1 f7 d1 41 01 cc 41 21 c4 e9 a9 00 00 00 e8 ca 49 01 f8 e9 9c 00 00 00 e8 c0 49 01 f8 44 89 e0 99 &amp;amp;lt;f7&amp;amp;gt; 7c 24 1c 41 29 d4 48 bb 00 00 00 00 00 fc ff df e9 80 00 00 00
RSP: 0018:ffffc90003017640 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88807b469e40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003017730 R08: ffff888033268143 R09: 1ffff1100664d028
R10: dffffc0000000000 R11: ffffed100664d029 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS:  000055557faa0500(0000) GS:ffff888126135000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;mptcp: Initialise rcv_mss before calling tcp_send_active_reset() in mptcp_do_fastclose().&lt;/p&gt;
&lt;p&gt;syzbot reported divide-by-zero in __tcp_select_window() by
MPTCP socket. [0]&lt;/p&gt;
&lt;p&gt;We had a similar issue for the bare TCP and fixed in commit
499350a5a6e7 (&amp;amp;quot;tcp: initialize rcv_mss to TCP_MIN_MSS instead
of 0&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s apply the same fix to mptcp_do_fastclose().&lt;/p&gt;
&lt;p&gt;[0]:
Oops: divide error: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6068 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__tcp_select_window+0x824/0x1320 net/ipv4/tcp_output.c:3336
Code: ff ff ff 44 89 f1 d3 e0 89 c1 f7 d1 41 01 cc 41 21 c4 e9 a9 00 00 00 e8 ca 49 01 f8 e9 9c 00 00 00 e8 c0 49 01 f8 44 89 e0 99 &amp;amp;lt;f7&amp;amp;gt; 7c 24 1c 41 29 d4 48 bb 00 00 00 00 00 fc ff df e9 80 00 00 00
RSP: 0018:ffffc90003017640 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88807b469e40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003017730 R08: ffff888033268143 R09: 1ffff1100664d028
R10: dffffc0000000000 R11: ffffed100664d029 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS:  000055557faa0500(0000) GS:ffff888126135000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1946</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31399</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31399</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 228 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvdimm/bus: Fix potential use after free in asynchronous initialization Dingisoul with KASAN reports a use after free if device_add() fails in nd_async_device_register(). Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while scheduling async init&amp;#34;) correctly added a reference on the parent device to be held until asynchronous initialization was complete.  However, if device_add() results in an allocation failure the ref count of the device drops to 0 prior to the parent pointer being accessed.  Thus resulting in use after free. The bug bot AI correctly identified the fix.  Save a reference to the parent pointer to be used to drop the parent reference regardless of the outcome of device_add().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 228 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvdimm/bus: Fix potential use after free in asynchronous initialization Dingisoul with KASAN reports a use after free if device_add() fails in nd_async_device_register(). Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while scheduling async init&amp;#34;) correctly added a reference on the parent device to be held until asynchronous initialization was complete.  However, if device_add() results in an allocation failure the ref count of the device drops to 0 prior to the parent pointer being accessed.  Thus resulting in use after free. The bug bot AI correctly identified the fix.  Save a reference to the parent pointer to be used to drop the parent reference regardless of the outcome of device_add().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31399</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0985 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0985</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um unter anderem einen Denial of Service-Angriff auszuführen oder um Sicherheitsmechanismen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um unter anderem einen Denial of Service-Angriff auszuführen oder um Sicherheitsmechanismen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0985</guid>
    </item>
  </channel>
</rss>
