accel/amdxdna: reject user command submission without a command BO

Summary

In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: reject user command submission without a command BO amdxdna_drm_submit_execbuf() passes the user-supplied command BO handle straight into amdxdna_cmd_submit() with drv_cmd == NULL. When the handle is AMDXDNA_INVALID_BO_HANDLE (0), the block that fetches job->cmd_bo is skipped, leaving it NULL, and no check rejects it on the user path (the !job->cmd_bo guard lives inside the != INVALID branch). The job is then armed and pushed to the DRM scheduler. aie2_sched_job_run() takes the drv_cmd == NULL path and calls amdxdna_cmd_set_state(job->cmd_bo) -> amdxdna_gem_vmap(NULL) -> to_gobj(NULL)->dev, a NULL pointer dereference in the drm_sched 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 AMDXDNA_EXEC_CMD ioctl (cmd_handles = 0). Only internal driver commands (SYNC_DEBUG_BO / ATTACH_DEBUG_BO) legitimately pass AMDXDNA_INVALID_BO_HANDLE, and they always set drv_cmd. Reject the invalid handle for user submissions (drv_cmd == NULL) at the submit choke point so every user path is covered. Found by 0sec automated security-research tooling (https://0sec.ai).

Timeline

1. Aug 15, 2026, 5:52 AM UTCCVE published
2. Oct 15, 2026, 10:08 AM UTCRecord last updated

Affected versions

• Linux Linux

  From aac243092b707bb3018e951d470cc1a9bcbaba6c · fixed in 241cf3b7455bebbe492b9df4912b48e3260061d4; From aac243092b707bb3018e951d470cc1a9bcbaba6c · fixed in fff6509d976f6fae423a5236391ccdbd7e0e9f06; From aac243092b707bb3018e951d470cc1a9bcbaba6c · fixed in 261c1fe3327ad24508f54552c6366e3e4db82c15

• Linux Linux

  6.14

• KernelLinux

  From 6.14.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.5

References 3