PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-93202 Linux CVE debrief

A vulnerability in the Linux kernel's i3c master device registration can lead to recursive locking and potential deadlocks. The issue arises from the i3c_master_register_new_i3c_devs() function registering newly discovered devices while holding the i3c_bus_normaluse_lock(). If a device's probe callback invokes I3C helpers that take i3c_bus_normaluse_lock() again, it can result in a recursive acquisition of the same rwsem, which is not supported by rwsems and can cause deadlocks.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-17
Original CVE updated
2026-10-30
Advisory published
2026-09-17
Advisory updated
2026-10-30

Who should care

Linux kernel maintainers, Linux distribution maintainers, and users of the Linux kernel, especially those using the i3c master device, should assess exposure and prioritize verification of affected systems.

Why it matters

A vulnerability in the Linux kernel's i3c master device registration can lead to recursive locking and potential deadlocks, requiring verification of affected systems and application of patches.

  • Defenders should verify if their systems are using affected versions of the Linux kernel
  • Defenders should review and apply patches to fix the recursive locking issue
  • Defenders should monitor system logs for potential deadlock warnings

Technical summary

The Linux kernel's i3c master device registration is vulnerable to recursive locking, potentially leading to deadlocks, due to the i3c_master_register_new_i3c_devs() function registering newly discovered devices while holding the i3c_bus_normaluse_lock(). This can cause issues when a device's probe callback invokes I3C helpers that take i3c_bus_normaluse_lock() again, resulting in a recursive acquisition of the same rwsem. Defenders should assess exposure and prioritize verification of affected systems, especially those using the i3c master device.

Defensive priority

Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems, especially those using the i3c master device.

Recommended defensive actions

  • Review and apply the provided patches to fix the recursive locking issue
  • Verify that affected systems are using the latest Linux kernel version
  • Monitor system logs for potential deadlock warnings
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, including a description of the issue and references to the relevant commits. Defenders should verify if their systems are using affected versions of the Linux kernel and review system logs for potential deadlock warnings. The i3c_master_register_new_i3c_devs() function registers newly discovered devices while holding the i3c_bus_normaluse_lock(), which can lead to recursive locking and potential deadlocks. Evidence is limited to public CVE details and may not reflect

Sources and references

Verified primary and authoritative sources

  • CVE-2026-93202 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-93202

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-93202 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93202

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • i3c: master: Fix recursive locking during device registration

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/93xxx/CVE-2026-93202.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/015fcf330c29803bbf92b719b4889ba74ecbbc71

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6640f778aa3d430e67171f8d17fe4a35bb44b578

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0200dc55e68cc0177b6e60919de415cc96fdd4e1

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b25232f66e8cd653d0c6bfdbe534e62a2f9d6a1b

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/9dc73c51ed3ee965c3ddb0ac31cf5c3eea68fa0c

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/456f832e5fc26fbfd3b8200fd4553eee520cc377

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.