Vulnerability · Published Sep 17, 2026 · Assigned by Linux

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

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 94.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-93202
Debian:13linux6.12.115-2DEBIAN-CVE-2026-93202
Debian:14linux7.2.6-1DEBIAN-CVE-2026-93202
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-93202
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-93202
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-93202
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-93202

Affected products (as reported)

VendorProductVersions
Linux Linux 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – before 015fcf330c29803bbf92b719b4889ba74ecbbc713a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – before 6640f778aa3d430e67171f8d17fe4a35bb44b5783a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – before 0200dc55e68cc0177b6e60919de415cc96fdd4e13a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – before b25232f66e8cd653d0c6bfdbe534e62a2f9d6a1b3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – before 9dc73c51ed3ee965c3ddb0ac31cf5c3eea68fa0c3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – before 456f832e5fc26fbfd3b8200fd4553eee520cc377
Linux Linux 5.0

References