{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72324 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72324 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-72324 and fix it if it is affected.\n\nWhat it is: CVE-2026-72324 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-72324 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-72324/ (Markdown: https://insights.sbomify.com/CVE-2026-72324/index.md)","id":"CVE-2026-72324","markdown":"https://insights.sbomify.com/CVE-2026-72324/index.md","name":"CVE-2026-72324","record":{"aliases":["AZL-96126","BELL-CVE-2026-72324","DEBIAN-CVE-2026-72324","GHSA-f4rp-fvp9-gmx9","UBUNTU-CVE-2026-72324"],"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":"none","summary":"A memory leak in the Linux kernel's mvebu GPIO driver during device unbinding can lead to resource exhaustion and denial of service.","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\ngpio: mvebu: free generic chips on unbind\n\nirq_alloc_domain_generic_chips() allocates generic chip data that must\nbe freed via irq_domain_remove_generic_chips(). The devres action\nmvebu_gpio_remove_irq_domain() only called irq_domain_remove(), which\nonly frees the generic chips if IRQ_DOMAIN_FLAG_DESTROY_GC is set.\nCall irq_domain_remove_generic_chips() explicitly before\nirq_domain_remove() instead.","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":"gpio: mvebu: free generic chips on unbind","id":"CVE-2026-72324","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"perf/x86/amd/core: Avoid enabling BRS from the SVM reload path","id":"CVE-2026-72325"},"packages":[],"prev":{"headline":"ipv4: igmp: Fix potential UAF in igmp_gq_start_timer()","id":"CVE-2026-72323"},"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-10-21","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's mvebu GPIO driver during device unbinding can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-72324/"}