VulnerabilityPublished 17 Sep 2026Updated 21 Oct 2026

CVE-2026-93202: Linux kernel · i3c: master: Fix recursive locking during device registration

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in b25232f66e8cd653d0c6bfdbe534e62a2f9d6a1b : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in b25232f66e8cd653d0c6bfdbe534e62a2f9d6a1b, 6640f778aa3d430e67171f8d17fe4a35bb44b578, 456f832e5fc26fbfd3b8200fd4553eee520cc377 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0, < b25232f66e8cd653d0c6bfdbe534e62a2f9d6a1b	Fixed in b25232f66e8cd653d0c6bfdbe534e62a2f9d6a1b
LinuxLinux	Affected ≥ 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0, < 6640f778aa3d430e67171f8d17fe4a35bb44b578	Fixed in 6640f778aa3d430e67171f8d17fe4a35bb44b578
LinuxLinux	Affected ≥ 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0, < 456f832e5fc26fbfd3b8200fd4553eee520cc377	Fixed in 456f832e5fc26fbfd3b8200fd4553eee520cc377
LinuxLinux	Affected ≥ 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0, < 0200dc55e68cc0177b6e60919de415cc96fdd4e1	Fixed in 0200dc55e68cc0177b6e60919de415cc96fdd4e1
LinuxLinux	Affected ≥ 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0, < 9dc73c51ed3ee965c3ddb0ac31cf5c3eea68fa0c	Fixed in 9dc73c51ed3ee965c3ddb0ac31cf5c3eea68fa0c
LinuxLinux	Affected =5.0	Fixed in–

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_match_id+0x45/0x370 but task is already holding lock: ffff88811c810d78 (&i3cbus->lock){++++}-{4:4}, at: i3c_master_reg_work_fn+0x21/0x5f0 Fix this by separating device creation from device registration. Populate desc->dev under the maintenance lock, collect the devices that still need registration into a local list, then release the lock before calling device_register(). Finally retake the lock and clean up any devices that failed to register. Use the maintenance lock rather than the normal-use lock while adding device objects. A write-side maintenance lock prevents readers from observing a partially initialized desc->dev during initial device population, or desc->dev disappearing if registration fails. The local list requires a list node, so add a list node member to struct i3c_device.

References

Community reviews

Loading reviews…