CVE-2026-93202

/// Technical description

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

i3c: master: Fix recursive locking during device registration

i3c_master_register_new_i3c_devs() registers newly discovered devices

while holding i3c_bus_normaluse_lock(), a down_read(). device_register()

can immediately probe the device, and probe callbacks typically invoke

I3C helpers that take i3c_bus_normaluse_lock() again, leading to a

recursive acquisition of the same rwsem. rwsems do not support recursive

read locking and can deadlock when a writer is waiting. See the

"Recursive read locks" section of Documentation/locking/lockdep-design.rst.

For example, with Intel LPSS I3C, LOCKDEP generates a WARNING like:

# echo intel-lpss-i3c.0 > /sys/bus/platform/drivers/mipi-i3c-hci/unbind

# echo intel-lpss-i3c.0 > /sys/bus/platform/drivers/mipi-i3c-hci/bind

WARNING: possible recursive locking detected

kworker/5:1/94 is trying to acquire lock:

ffff88811c810d78 (&i3cbus->lock){++++}-{4:4}, at: i3c_device_ma

/// 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