Description
In the Linux kernel, the following vulnerability has been resolved:

i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev()

i3c_hci_addr_to_dev() walks bus->devs.i3c, which is protected by
bus.lock (rwsem). However, it is invoked from the MIPI I3C HCI IRQ
handler, which cannot take bus.lock. This allows concurrent device
addition/removal in the I3C core to modify the list while it is being
traversed, potentially leading to use-after-free or crashes.

Remove the dependency on the bus device list and introduce a dedicated
lookup table. Add an ibi_devs[] array indexed by DAT entry, maintained
under hci->lock. Update the array when IBIs are enabled or disabled,
so that it always reflects the set of devices allowed to generate IBIs.
Also update when IBIs are freed, to cover the corner case when an IBI is
freed without first being disabled (e.g. oldedev in
i3c_master_add_i3c_dev_locked()).

Move i3c_hci_addr_to_dev() into core.c, reimplement it using the new
array, and add a lockdep assertion to enforce that hci->lock is held
by callers.

Demote a message in PIO and DMA IBI handling, from an error to a debug
message, because there is a race window when the condition can arise
normally.
Published: 2026-08-15
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A race condition in the Linux kernel’s I3C and MIPI I3C HCI driver allows concurrent modification of the device list from normal code paths while the interrupt handler walks that list. Because the handler cannot acquire the bus lock, a thread adding or removing a device can corrupt the list during traversal, potentially causing a use‑after‑free or kernel crash. The weakness comprises race condition and improper resource handling as reflected in CWE-364.

Affected Systems

All Linux kernel builds that include the i3c and MIPI I3C HCI driver before the patch commit are affected. This includes every kernel release that compiles these modules and exposes the MIPI I3C HCI path; any system running such a kernel without the fix is impacted.

Risk and Exploitability

The vulnerability carries a CVSS score of 7.8 and an EPSS less than 1 %, indicating a low but non‑zero exploitation probability. It is not listed in the CISA KEV catalog. The likely attack vector is a local or privileged adversary that can trigger I3C traffic to cause device addition or removal during an interrupt, leading to a race. If the MIPI I3C HCI feature remains enabled, the risk to system availability is high because a single crash can bring the entire kernel down.

Generated by OpenCVE AI on August 17, 2026 at 18:30 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the patch commit that fixes i3c_hci_addr_to_dev() or upgrade to a kernel version that includes the change.
  • Rebuild and reload the kernel image with the updated driver after applying the patch.
  • If MIPI I3C HCI functionality is not required, disable the feature through kernel configuration or via sysfs to reduce exposure.

Generated by OpenCVE AI on August 17, 2026 at 18:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 17 Aug 2026 16:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-416

Mon, 17 Aug 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-364
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Sat, 15 Aug 2026 19:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-416

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev() i3c_hci_addr_to_dev() walks bus->devs.i3c, which is protected by bus.lock (rwsem). However, it is invoked from the MIPI I3C HCI IRQ handler, which cannot take bus.lock. This allows concurrent device addition/removal in the I3C core to modify the list while it is being traversed, potentially leading to use-after-free or crashes. Remove the dependency on the bus device list and introduce a dedicated lookup table. Add an ibi_devs[] array indexed by DAT entry, maintained under hci->lock. Update the array when IBIs are enabled or disabled, so that it always reflects the set of devices allowed to generate IBIs. Also update when IBIs are freed, to cover the corner case when an IBI is freed without first being disabled (e.g. oldedev in i3c_master_add_i3c_dev_locked()). Move i3c_hci_addr_to_dev() into core.c, reimplement it using the new array, and add a lockdep assertion to enforce that hci->lock is held by callers. Demote a message in PIO and DMA IBI handling, from an error to a debug message, because there is a race window when the condition can arise normally.
Title i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:44:23.013Z

Reserved: 2026-08-09T03:40:39.932Z

Link: CVE-2026-72454

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:19.387

Modified: 2026-08-17T06:19:13.003

Link: CVE-2026-72454

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-72454 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-17T18:45:04Z

Weaknesses
  • CWE-364

    Signal Handler Race Condition