CVE-2026-72454
Last modified
CVE-2026-72454 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9ad9a52cce2828d932ae9495181e3d6414f72c07, < 8f851cab401c28287d536b1347d76f6e219c0db6; >= 9ad9a52cce2828d932ae9495181e3d6414f72c07, < 650716f23eac488c6696babdc7805f6a6b7427ad |
| Linux | Linux | 5.11 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72454?
How severe is CVE-2026-72454?
How do I fix CVE-2026-72454?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72448In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72449In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72450In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72451In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72452In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72453In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72455In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-72456In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72457In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72458In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72459In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-7246This CVE record was assigned not following CNA/CVE rules and…7.2
Are you affected by CVE-2026-72454?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
