<?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>Thu, 15 Oct 2026 02:07:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56670 — usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-56670</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer&lt;/p&gt;
&lt;p&gt;Considering that in some extreme cases,
when u_serial driver is accessed by multiple threads,
Thread A is executing the open operation and calling the gs_open,
Thread B is executing the disconnect operation and calling the
gserial_disconnect function,The port-&amp;gt;port_usb pointer will be set to NULL.&lt;/p&gt;
&lt;p&gt;E.g.
    Thread A                                 Thread B
    gs_open()                                gadget_unbind_driver()
    gs_start_io()                            composite_disconnect()
    gs_start_rx()                            gserial_disconnect()
    ...                                      ...
    spin_unlock(&amp;amp;port-&amp;gt;port_lock)
    status = usb_ep_queue()                  spin_lock(&amp;amp;port-&amp;gt;port_lock)
    spin_lock(&amp;amp;port-&amp;gt;port_lock)              port-&amp;gt;port_usb = NULL
    gs_free_requests(port-&amp;gt;port_usb-&amp;gt;in)     spin_unlock(&amp;amp;port-&amp;gt;port_lock)
    Crash&lt;/p&gt;
&lt;p&gt;This causes thread A to access a null pointer (port-&amp;gt;port_usb is null)
when calling the gs_free_requests function, causing a crash.&lt;/p&gt;
&lt;p&gt;If port_usb is NULL, the release request will be skipped as it
will be done by gserial_disconnect.&lt;/p&gt;
&lt;p&gt;So add a null pointer check to gs_start_io before attempting
to access the value of the pointer port-&amp;gt;port_usb.&lt;/p&gt;
&lt;p&gt;Call trace:
 gs_start_io+0x164/0x25c
 gs_open+0x108/0x13c
 tty_open+0x314/0x638
 chrdev_open+0x1b8/0x258
 do_dentry_open+…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer&lt;/p&gt;
&lt;p&gt;Considering that in some extreme cases,
when u_serial driver is accessed by multiple threads,
Thread A is executing the open operation and calling the gs_open,
Thread B is executing the disconnect operation and calling the
gserial_disconnect function,The port-&amp;gt;port_usb pointer will be set to NULL.&lt;/p&gt;
&lt;p&gt;E.g.
    Thread A                                 Thread B
    gs_open()                                gadget_unbind_driver()
    gs_start_io()                            composite_disconnect()
    gs_start_rx()                            gserial_disconnect()
    ...                                      ...
    spin_unlock(&amp;amp;port-&amp;gt;port_lock)
    status = usb_ep_queue()                  spin_lock(&amp;amp;port-&amp;gt;port_lock)
    spin_lock(&amp;amp;port-&amp;gt;port_lock)              port-&amp;gt;port_usb = NULL
    gs_free_requests(port-&amp;gt;port_usb-&amp;gt;in)     spin_unlock(&amp;amp;port-&amp;gt;port_lock)
    Crash&lt;/p&gt;
&lt;p&gt;This causes thread A to access a null pointer (port-&amp;gt;port_usb is null)
when calling the gs_free_requests function, causing a crash.&lt;/p&gt;
&lt;p&gt;If port_usb is NULL, the release request will be skipped as it
will be done by gserial_disconnect.&lt;/p&gt;
&lt;p&gt;So add a null pointer check to gs_start_io before attempting
to access the value of the pointer port-&amp;gt;port_usb.&lt;/p&gt;
&lt;p&gt;Call trace:
 gs_start_io+0x164/0x25c
 gs_open+0x108/0x13c
 tty_open+0x314/0x638
 chrdev_open+0x1b8/0x258
 do_dentry_open+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-56670</guid>
    </item>
    <item>
      <title>USN-7379-1 — linux, linux-aws, linux-azure, linux-gcp, linux-hwe-6.11, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7379-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&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;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.11&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;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Virtio block driver;
  - Bluetooth drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I3C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Microchip PCI driver;
  - MTD block device drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - i.MX PM domains;
  - Power supply drivers;
  - Voltage and Current Regulator drivers;
  - SCSI subsystem;
  - i.MX SoC drivers;
  - SPI subsystem;
  - UFS subsystem;
  - USB Gadget drivers;
  - TDX Guest driver;
  - AFS file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - F2FS file system;
  - JFFS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7379-1</guid>
    </item>
  </channel>
</rss>
