{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72384 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72384 is an use after free 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-72384 and fix it if it is affected.\n\nWhat it is: CVE-2026-72384 is an use after free 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-72384 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-72384/ (Markdown: https://insights.sbomify.com/CVE-2026-72384/index.md)","id":"CVE-2026-72384","markdown":"https://insights.sbomify.com/CVE-2026-72384/index.md","name":"CVE-2026-72384","record":{"aliases":["BELL-CVE-2026-72384","DEBIAN-CVE-2026-72384","GHSA-xcpr-v9rp-m43f","UBUNTU-CVE-2026-72384"],"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":"high_privilege","summary":"A missing cleanup in the ts4800 irqchip driver allows a use-after-free condition, potentially causing kernel crashes or code execution upon driver removal.","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/ts4800: Fix missing chained handler cleanup on remove\n\nThe driver installs a chained handler for the parent interrupt during probe\nusing irq_set_chained_handler_and_data(), but the remove function does not\nclear this handler. This leaves a dangling handler that may be called when\nthe parent interrupt fires after the driver has been removed, potentially\naccessing freed memory and causing a kernel crash.\n\nAdditionally, the parent_irq obtained via irq_of_parse_and_map() is not\nstored, making it inaccessible in the remove function. Moreover, interrupt\nmappings created during probe are not properly disposed.\n\nFix this by:\n\n   - Saving parent_irq in probe\n   - Clearing the chained handler with NULL in ts4800_ic_remove()\n   - Disposing all IRQ mappings before domain removal to prevent resource\n     leaks","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/ts4800: Fix missing chained handler cleanup on remove","id":"CVE-2026-72384","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"tracing/fprobe: Fix NULL pointer dereference in fprobe_fgraph_entry()","id":"CVE-2026-72385"},"packages":[],"prev":{"headline":"sctp: fix addr_wq_timer race in sctp_free_addr_wq()","id":"CVE-2026-72383"},"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 missing cleanup in the ts4800 irqchip driver allows a use-after-free condition, potentially causing kernel crashes or code execution upon driver removal.","url":"https://insights.sbomify.com/CVE-2026-72384/"}