{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72454 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72454 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72454 and fix it if it is affected.\n\nWhat it is: CVE-2026-72454 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72454 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72454/ (Markdown: https://insights.sbomify.com/CVE-2026-72454/index.md)","id":"CVE-2026-72454","markdown":"https://insights.sbomify.com/CVE-2026-72454/index.md","name":"CVE-2026-72454","record":{"aliases":["BELL-CVE-2026-72454","DEBIAN-CVE-2026-72454","GHSA-48cg-fm56-jr4v","UBUNTU-CVE-2026-72454"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel I3C HCI driver allows concurrent list modification, potentially causing use-after-free crashes or code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev()\n\ni3c_hci_addr_to_dev() walks bus-\u003edevs.i3c, which is protected by\nbus.lock (rwsem).  However, it is invoked from the MIPI I3C HCI IRQ\nhandler, which cannot take bus.lock.  This allows concurrent device\naddition/removal in the I3C core to modify the list while it is being\ntraversed, potentially leading to use-after-free or crashes.\n\nRemove the dependency on the bus device list and introduce a dedicated\nlookup table.  Add an ibi_devs[] array indexed by DAT entry, maintained\nunder hci-\u003elock.  Update the array when IBIs are enabled or disabled,\nso that it always reflects the set of devices allowed to generate IBIs.\nAlso update when IBIs are freed, to cover the corner case when an IBI is\nfreed without first being disabled (e.g. oldedev in\ni3c_master_add_i3c_dev_locked()).\n\nMove i3c_hci_addr_to_dev() into core.c, reimplement it using the new\narray, and add a lockdep assertion to enforce that hci-\u003elock is held\nby callers.\n\nDemote a message in PIO and DMA IBI handling, from an error to a debug\nmessage, because there is a race window when the condition can arise\nnormally.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev()","id":"CVE-2026-72454","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"apparmor: fix uninitialised pointer passed to audit_log_untrustedstring()","id":"CVE-2026-72455"},"packages":[],"prev":{"headline":"regcache: Do not overwrite error code when finalizing cache after error","id":"CVE-2026-72453"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A race condition in the Linux kernel I3C HCI driver allows concurrent list modification, potentially causing use-after-free crashes or code execution.","url":"https://insights.sbomify.com/CVE-2026-72454/"}