VulnerabilityPublished 15 Aug 2026Updated 9 Oct 2026

CVE-2026-72332: Linux kernel · accel/amdxdna: Prevent PM resume deadlock in hwctx_sync_debug_bo()

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 7.0.0-1014.14~24.04.1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.0-1014.14~24.04.1, 7.0.0-1017.17~24.04.1, 7.0.0-1016.16~24.04.1 +11

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-g8r2-47gx-v4q8

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-38.38	Fixed in 7.0.0-38.38
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1017.17	Fixed in 7.0.0-1017.17
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1016.16	Fixed in 7.0.0-1016.16
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1008.9	Fixed in 7.0.0-1008.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available that resolves this deadlock by changing the order of lock acquisition and function calls in the affected driver code. Users should apply the official Linux kernel updates that include this fix. The vendor advisory confirms the availability of this fix. No additional mitigation steps are indicated.

Description

A deadlock vulnerability was identified and resolved in the Linux kernel's AMD XDNA acceleration driver. The issue occurs when the hardware callback function hwctx_sync_debug_bo() holds a device lock and calls functions that may attempt to reacquire the same lock during power management resume operations, causing a deadlock. This flaw affects specific Linux kernel versions and has been fixed by reordering calls to avoid the deadlock condition.

Impact

This vulnerability could cause the system to deadlock during power management resume operations involving the AMD XDNA acceleration driver, potentially leading to system hangs or degraded availability. There is no indication of code execution or privilege escalation. No known exploits in the wild have been reported.

Summary

The Linux kernel's AMD XDNA acceleration driver contained a deadlock vulnerability in the function amdxdna_hwctx_sync_debug_bo(). This function invoked the hardware callback hwctx_sync_debug_bo() while holding the xdna->dev_lock. The callback could call amdxdna_cmd_submit(), which calls amdxdna_pm_resume_get(). If the device was suspended, amdxdna_pm_resume_get() might synchronously execute amdxdna_pm_resume(), which also acquires xdna->dev_lock, leading to a deadlock. The fix involved calling amdxdna_pm_resume_get() before acquiring xdna->dev_lock in both amdxdna_hwctx_sync_debug_bo() and amdxdna_drm_config_hwctx_ioctl(), preventing the deadlock scenario.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 08:11 UTC

Technical details

References

Community reviews

Related threats