CVE-2026-93202: i3c: master: Fix recursive locking during device registration
Published Sep 17, 2026
·Updated
i3c: master: Fix recursive locking during device registration
Affected Software
1 affected component
Linux Kernel
Event History
Sep 17, 2026
CVE Published
via MITRE·04:12 PM
Data Sourced
via MITRE·04:12 PM
Description
Data Sourced
via NVD·05:18 PM
Description
Sep 19, 2026
Data Sourced
via Microsoft·08:06 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
Which systems are realistically exposed to this issue?
Systems using the Linux kernel I3C subsystem and registering newly discovered I3C devices are affected by the described locking path. The report demonstrates the condition with Intel LPSS I3C.
2
What event triggers the deadlock condition?
The condition occurs when device registration immediately invokes a probe callback that calls I3C helpers while i3c_bus_normaluse_lock() is already held for reading. A recursive read-lock acquisition can deadlock when a writer is waiting.
3
How can an administrator identify this condition?
Kernel lockdep may report a "possible recursive locking detected" warning involving the I3C bus lock. The example reproduces this by unbinding and rebinding an Intel LPSS I3C device through its platform-driver sysfs entries.