<?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://db.gcve.eu</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, 19 Nov 2026 17:30:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-43098 — i3c: Use i3cdev-&gt;desc-&gt;info instead of calling i3c_device_get_info() to avoid deadlock</title>
      <link>https://db.gcve.eu/vuln/cve-2024-43098</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;i3c: Use i3cdev-&amp;gt;desc-&amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;i3cbus-&amp;gt;lock twice. See the log below.
Use i3cdev-&amp;gt;desc-&amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;i3cbus-&amp;gt;lock);
  lock(&amp;amp;i3cbus-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;dev-&amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0x32ec
 lock_acquire+0x134/0x2b0
 down_read+0x50/0x19c
 i3c_bus_normaluse_lock+0x14/0x24
 i3c_device_get_info+0x24/0x58
 i3c_device_ueve…&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;i3c: Use i3cdev-&amp;gt;desc-&amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;i3cbus-&amp;gt;lock twice. See the log below.
Use i3cdev-&amp;gt;desc-&amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;i3cbus-&amp;gt;lock);
  lock(&amp;amp;i3cbus-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;dev-&amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0x32ec
 lock_acquire+0x134/0x2b0
 down_read+0x50/0x19c
 i3c_bus_normaluse_lock+0x14/0x24
 i3c_device_get_info+0x24/0x58
 i3c_device_ueve…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-43098</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://db.gcve.eu/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://db.gcve.eu/vuln/usn-7379-1</guid>
    </item>
  </channel>
</rss>
