{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72153 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72153 is a memory corruption 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-72153 and fix it if it is affected.\n\nWhat it is: CVE-2026-72153 is a memory corruption 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-72153 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-72153/ (Markdown: https://insights.sbomify.com/CVE-2026-72153/index.md)","id":"CVE-2026-72153","markdown":"https://insights.sbomify.com/CVE-2026-72153/index.md","name":"CVE-2026-72153","record":{"aliases":["BELL-CVE-2026-72153","DEBIAN-CVE-2026-72153","GHSA-cjfc-rqm4-h9mg","UBUNTU-CVE-2026-72153"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A Linux kernel bug in the crossbar IRQ chip driver causes incorrect index usage, potentially leading to out-of-bounds memory access and system instability.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/crossbar: Use correct index in crossbar_domain_free()\n\ncrossbar_domain_free() resets the domain data and then uses the nulled\nout irq_data-\u003ehwirq member as index to reset the irq_map[] entry and to\nwrite the relevant crossbar register with a safe entry. That means it\nnever frees the correct index and keeps the crossbar register connection\nto the source interrupt active.\n\nIf it would not reset the domain data, then this would be even worse as\nirq_data-\u003ehwirq holds the source interrupt number, but both the map and\nregister index need the corresponding GIC SPI number and not the source\ninterrupt number. This might even result in an out of bounds access as\nthe source interrupt number can be higher than the maximal index space.\n\nFix this by using the GIC SPI index from the parent domain's irq_data.","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":"irqchip/crossbar: Use correct index in crossbar_domain_free()","id":"CVE-2026-72153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"openrisc: Fix jump_label smp syncing","id":"CVE-2026-72154"},"packages":[],"prev":{"headline":"tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat()","id":"CVE-2026-72152"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A Linux kernel bug in the crossbar IRQ chip driver causes incorrect index usage, potentially leading to out-of-bounds memory access and system instability.","url":"https://insights.sbomify.com/CVE-2026-72153/"}