{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93072 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93072 is an use after free vulnerability in Linux, published on 17 Sep 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-93072 and fix it if it is affected.\n\nWhat it is: CVE-2026-93072 is an use after free vulnerability in Linux, published on 17 Sep 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-93072 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-93072/ (Markdown: https://insights.sbomify.com/CVE-2026-93072/index.md)","id":"CVE-2026-93072","markdown":"https://insights.sbomify.com/CVE-2026-93072/index.md","name":"CVE-2026-93072","record":{"aliases":["AZL-102342","BELL-CVE-2026-93072","DEBIAN-CVE-2026-93072","GHSA-h6q6-g8xj-rf6w","UBUNTU-CVE-2026-93072"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A use-after-free in the Renesas IRQC driver can cause a kernel crash when the driver is removed, requiring local privileged access to trigger.","user_interaction":"not_required","vuln_class":"use_after_free"},"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/renesas-irqc: Fix generic interrupt chip leak on remove\n\nThe driver allocates domain generic chips probe. However, on driver\nremoval, the generic chips are not automatically freed when the interrupt\ndomain is removed because the domain flags do not include\nIRQ_DOMAIN_FLAG_DESTROY_GC.\n\nThis causes both the domain generic chips structure and the associated\ngeneric chips to be leaked. Additionally, the generic chips remain on the\nglobal list and may later be accessed by generic interrupt chip suspend,\nresume, or shutdown callbacks after the driver has been removed,\npotentially resulting in a use-after-free and kernel crash.\n\nFix the resource leak by setting IRQ_DOMAIN_FLAG_DESTROY_GC on the\ninterrupt domain; this lets the interrupt domain core automatically\nrelease all generic chips when irq_domain_remove() is invoked, removing\nthe need for manual cleanup calls in error paths and remove callback.","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/renesas-irqc: Fix generic interrupt chip leak on remove","id":"CVE-2026-93072","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"dax: read holder_ops once in dax_holder_notify_failure()","id":"CVE-2026-93073"},"packages":[],"prev":{"headline":"media: bcm2835-unicam: Fix asc leaked in error/remove path","id":"CVE-2026-93071"},"products":["Linux"],"published":"2026-09-17","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-10-19","vendors":["Linux"]},"summary":"A use-after-free in the Renesas IRQC driver can cause a kernel crash when the driver is removed, requiring local privileged access to trigger.","url":"https://insights.sbomify.com/CVE-2026-93072/"}