VulnerabilityPublished 15 Aug 2026Updated 9 Oct 2026

CVE-2026-72091: Linux kernel · accel/amdxdna: reject user command submission without a command 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.2% chance of exploitation in 30 days – higher than 10% 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-jvc7-qr5g-mx5f

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

An official patch is available that rejects invalid user command submissions lacking a valid command buffer object handle. Users should apply the updated Linux kernel versions that include this fix. No additional mitigations are required as the patch addresses the root cause.

Description

A vulnerability in the Linux kernel's AMD XDNA acceleration driver allowed user command submissions without a valid command buffer object (BO), leading to a NULL pointer dereference and kernel oops. This flaw was due to insufficient validation of user-supplied command BO handles, permitting a process with access to the accel node on systems with AMD NPU to trigger a kernel crash via a crafted ioctl call. The issue has been resolved by rejecting invalid handles at the submission point.

Impact

A local attacker with access to the accel node on a system with a probed AMD Neural Processing Unit (NPU) can trigger a kernel crash (kernel oops) by submitting a crafted command with an invalid buffer object handle. This results in a denial of service due to the NULL pointer dereference in the kernel scheduler worker thread. There is no indication of privilege escalation or arbitrary code execution from this vulnerability.

Summary

The Linux kernel's accel/amdxdna driver did not properly reject user command submissions lacking a valid command buffer object (BO). Specifically, the function amdxdna_drm_submit_execbuf() passed a user-supplied BO handle directly to amdxdna_cmd_submit() without checking if the handle was AMDXDNA_INVALID_BO_HANDLE (0). When this invalid handle was used, the job's command BO pointer remained NULL, bypassing user path validation. This led to a NULL pointer dereference in the drm_sched worker thread when the job was processed, causing a kernel oops. Only internal driver commands legitimately use the invalid handle with a set driver command, but user submissions with a NULL driver command were not rejected. The fix enforces rejection of such invalid handles for user submissions, preventing the kernel crash. The vulnerability affects specific Linux kernel versions including multiple 4.15.x, 5.0.x, and 5.3.x builds.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 06:38 UTC

Technical details

References

Community reviews

Related threats