UBUNTU-CVE-2026-72091: Null Pointer Dereference
In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: reject user command submission without a command BO amdxdnadrmsubmitexecbuf() passes the user-supplied command BO handle straight into amdxdnacmdsubmit() with drvcmd == NULL. When the handle is AMDXDNAINVALIDBOHANDLE (0), the block that fetches job->cmdbo is skipped, leaving it NULL, and no check rejects it on the user path (the !job->cmdbo guard lives inside the != INVALID branch). The job is then armed and pushed to the DRM scheduler. aie2schedjobrun() takes the drvcmd == NULL path and calls amdxdnacmdsetstate(job->cmdbo) -> amdxdnagemvmap(NULL) -> togobj(NULL)->dev, a NULL pointer dereference in the drmsched worker. A process with access to the accel node on a system with a probed AMD NPU can trigger a kernel oops with a single AMDXDNAEXECCMD ioctl (cmdhandles = 0). Only internal driver commands (SYNCDEBUGBO / ATTACHDEBUGBO) legitimately pass AMDXDNAINVALIDBOHANDLE, and they always set drvcmd. Reject the invalid handle for user submissions (drvcmd == NULL) at the submit choke point so every user path is covered. Found by 0sec automated security-research tooling (https://0sec.ai).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38~24.04.4 - Upgrade
Upgrade
ubuntu/linux-nvidia-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1024.25~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-38.38 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-nvidia-bosto a version that resolves this vulnerability.Fixed in 7.0.0-2022.23 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Compensating control
At the amdxdna command-submission choke point, reject AMDXDNA_INVALID_BO_HANDLE (0) for user submissions when drv_cmd == NULL; allow this handle only for internal SYNC_DEBUG_BO and ATTACH_DEBUG_BO commands that set drv_cmd.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Exposure requires a system with a probed AMD NPU and a process that can access the accel device node. The affected Ubuntu kernel packages listed are linux-riscv, linux-realtime, linux-hwe-edge, linux-azure, linux-gcp, linux-azure-fde, linux-gke, and linux-aws-5.0.
What does an attacker need to trigger the failure?
A local process needs access to the accel node. It can trigger the NULL pointer dereference with a single AMDXDNA_EXEC_CMD ioctl that supplies a command handle of 0.
What operational symptom indicates attempted or successful exploitation?
The malformed submission can cause a kernel oops in the DRM scheduler worker when the driver processes the job without a command buffer object. The described outcome is a NULL pointer dereference rather than execution of an internal driver command.