CVE-2024-43098

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

i3c: Use i3cdev->desc->info instead of calling i3c_device_get_info() to avoid deadlock

A deadlock may happen since the i3c_master_register() acquires

&i3cbus->lock twice. See the log below.

Use i3cdev->desc->info instead of calling i3c_device_info() to

avoid acquiring the lock twice.

v2:

- Modified the title and commit message

============================================

WARNING: possible recursive locking detected

6.11.0-mainline

--------------------------------------------

init/1 is trying to acquire lock:

f1ffff80a6a40dc0 (&i3cbus->lock){++++}-{3:3}, at: i3c_bus_normaluse_lock

but task is already holding lock:

f1ffff80a6a40dc0 (&i3cbus->lock){++++}-{3:3}, at: i3c_master_register

other info that might help us debug this:

Possible unsafe locking scenario:

CPU0

----

lock(&i3cbus->lock);

lock(&i3cbus->lock);

*** DEADLOCK ***

May be due to missing lock nesting notation

2 locks held by ini

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References