Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – < 015fcf330c29803bbf92b719b4889ba74ecbbc71
    • affected 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – < 6640f778aa3d430e67171f8d17fe4a35bb44b578
    • affected 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – < 0200dc55e68cc0177b6e60919de415cc96fdd4e1
    • affected 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – < b25232f66e8cd653d0c6bfdbe534e62a2f9d6a1b
    • affected 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – < 9dc73c51ed3ee965c3ddb0ac31cf5c3eea68fa0c
    • affected 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 – < 456f832e5fc26fbfd3b8200fd4553eee520cc377
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93202 badge
[![CVE-2026-93202](https://cveledger.app/badge/CVE-2026-93202.svg)](https://cveledger.app/cve/CVE-2026-93202)

Record last updated .