i3c: Use i3cdev->desc->info instead of calling i3c_device_get_info() to avoid deadlock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 · < 1f51ae217d09c361ede900b94735a6d2df6c0344| No fix yet |
| Linux Linux |
|
|
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);
From the CVE record · Linux
The Linux kernel’s I3C device registration path may acquire the same bus lock twice, causing a deadlock. The reported case occurred during driver initialization; the input does not describe an attacker-controlled trigger or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with I3C support should check their installations; affected versions are not specified.