{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72332 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72332 is a 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-72332 and fix it if it is affected.\n\nWhat it is: CVE-2026-72332 is a 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-72332 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-72332/ (Markdown: https://insights.sbomify.com/CVE-2026-72332/index.md)","id":"CVE-2026-72332","markdown":"https://insights.sbomify.com/CVE-2026-72332/index.md","name":"CVE-2026-72332","record":{"aliases":["DEBIAN-CVE-2026-72332","GHSA-g8r2-47gx-v4q8","UBUNTU-CVE-2026-72332"],"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":"low_privilege","summary":"A local attacker can trigger a deadlock in the AMD XDNA driver during power management resume, causing a system denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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\naccel/amdxdna: Prevent PM resume deadlock in hwctx_sync_debug_bo()\n\namdxdna_hwctx_sync_debug_bo() invokes the hardware hwctx_sync_debug_bo()\ncallback while holding xdna-\u003edev_lock.\n\nThe callback may call amdxdna_cmd_submit(), which in turn calls\namdxdna_pm_resume_get(). If the device is suspended,\namdxdna_pm_resume_get() may synchronously execute amdxdna_pm_resume(),\nwhich also acquires xdna-\u003edev_lock, resulting in a deadlock.\n\nAvoid the deadlock by calling amdxdna_pm_resume_get() before holding\nxdna-\u003edev_lock in both amdxdna_hwctx_sync_debug_bo() and\namdxdna_drm_config_hwctx_ioctl()","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":"accel/amdxdna: Prevent PM resume deadlock in hwctx_sync_debug_bo()","id":"CVE-2026-72332","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Bluetooth: L2CAP: fix tx ident leak for commands without a response","id":"CVE-2026-72333"},"packages":[],"prev":{"headline":"accel/amdxdna: Fix VMA access race","id":"CVE-2026-72331"},"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 local attacker can trigger a deadlock in the AMD XDNA driver during power management resume, causing a system denial of service.","url":"https://insights.sbomify.com/CVE-2026-72332/"}