<?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>Fri, 16 Oct 2026 21:06:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58009 — Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-58009</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc&lt;/p&gt;
&lt;p&gt;A NULL sock pointer is passed into l2cap_sock_alloc() when it is called
from l2cap_sock_new_connection_cb() and the error handling paths should
also be aware of it.&lt;/p&gt;
&lt;p&gt;Seemingly a more elegant solution would be to swap bt_sock_alloc() and
l2cap_chan_create() calls since they are not interdependent to that moment
but then l2cap_chan_create() adds the soon to be deallocated and still
dummy-initialized channel to the global list accessible by many L2CAP
paths. The channel would be removed from the list in short period of time
but be a bit more straight-forward here and just check for NULL instead of
changing the order of function calls.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE static
analysis tool.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc&lt;/p&gt;
&lt;p&gt;A NULL sock pointer is passed into l2cap_sock_alloc() when it is called
from l2cap_sock_new_connection_cb() and the error handling paths should
also be aware of it.&lt;/p&gt;
&lt;p&gt;Seemingly a more elegant solution would be to swap bt_sock_alloc() and
l2cap_chan_create() calls since they are not interdependent to that moment
but then l2cap_chan_create() adds the soon to be deallocated and still
dummy-initialized channel to the global list accessible by many L2CAP
paths. The channel would be removed from the list in short period of time
but be a bit more straight-forward here and just check for NULL instead of
changing the order of function calls.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE static
analysis tool.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-58009</guid>
    </item>
    <item>
      <title>USN-7516-1 — linux, linux-azure-5.4, linux-gcp, linux-gcp-5.4, linux-oracle vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7516-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - Block layer subsystem;
  - Drivers core;
  - Network block device driver;
  - Character device driver;
  - GPU drivers;
  - HID subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - Network drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - RapidIO drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - Trusted Execution Environment drivers;
  - USB DSL drivers;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - File systems infrastructure;
  - BTRFS file system;
  - NILFS2 file system;
  - UBI file system;
  - KVM subsystem;
  - L3 Master device support module;
  - Process Accounting mechanism;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Memory management;
  - 802.1Q VLAN protocol;
  - B.A.T.M.A.N. meshing protocol;
  - Bluetooth subsystem;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - Logical Link layer;
  - NFC subsystem;
  - Open vSwitch;
  - Rose network layer;
  - Network traffic control;
  - Wireless networking;
  - Tomoyo security module;
(CVE-2025-21866, CVE-2025-21846, CVE-2025-21971, CVE-2025-21…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - Block layer subsystem;
  - Drivers core;
  - Network block device driver;
  - Character device driver;
  - GPU drivers;
  - HID subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - Network drivers;
  - PPS (Pulse Per Second) driver;
  - PTP clock framework;
  - RapidIO drivers;
  - Real Time Clock drivers;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - Trusted Execution Environment drivers;
  - USB DSL drivers;
  - USB Device Class drivers;
  - USB core drivers;
  - USB Gadget drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - File systems infrastructure;
  - BTRFS file system;
  - NILFS2 file system;
  - UBI file system;
  - KVM subsystem;
  - L3 Master device support module;
  - Process Accounting mechanism;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Memory management;
  - 802.1Q VLAN protocol;
  - B.A.T.M.A.N. meshing protocol;
  - Bluetooth subsystem;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - Logical Link layer;
  - NFC subsystem;
  - Open vSwitch;
  - Rose network layer;
  - Network traffic control;
  - Wireless networking;
  - Tomoyo security module;
(CVE-2025-21866, CVE-2025-21846, CVE-2025-21971, CVE-2025-21…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7516-1</guid>
    </item>
  </channel>
</rss>
