FKIE_CVE-2026-72091
Vulnerability from fkie_nvd - Published: 2026-08-15 06:21 - Updated: 2026-08-17 06:18
Severity
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).
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/accel/amdxdna/amdxdna_ctx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "fff6509d976f6fae423a5236391ccdbd7e0e9f06",
"status": "affected",
"version": "aac243092b707bb3018e951d470cc1a9bcbaba6c",
"versionType": "git"
},
{
"lessThan": "261c1fe3327ad24508f54552c6366e3e4db82c15",
"status": "affected",
"version": "aac243092b707bb3018e951d470cc1a9bcbaba6c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/accel/amdxdna/amdxdna_ctx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.14"
},
{
"lessThan": "6.14",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/amdxdna: reject user command submission without a command BO\n\namdxdna_drm_submit_execbuf() passes the user-supplied command BO handle\nstraight into amdxdna_cmd_submit() with drv_cmd == NULL. When the handle\nis AMDXDNA_INVALID_BO_HANDLE (0), the block that fetches job-\u003ecmd_bo is\nskipped, leaving it NULL, and no check rejects it on the user path (the\n!job-\u003ecmd_bo guard lives inside the != INVALID branch).\n\nThe job is then armed and pushed to the DRM scheduler.\naie2_sched_job_run() takes the drv_cmd == NULL path and calls\namdxdna_cmd_set_state(job-\u003ecmd_bo) -\u003e amdxdna_gem_vmap(NULL) -\u003e\nto_gobj(NULL)-\u003edev, a NULL pointer dereference in the drm_sched worker.\nA process with access to the accel node on a system with a probed AMD NPU\ncan trigger a kernel oops with a single AMDXDNA_EXEC_CMD ioctl\n(cmd_handles = 0).\n\nOnly internal driver commands (SYNC_DEBUG_BO / ATTACH_DEBUG_BO)\nlegitimately pass AMDXDNA_INVALID_BO_HANDLE, and they always set drv_cmd.\nReject the invalid handle for user submissions (drv_cmd == NULL) at the\nsubmit choke point so every user path is covered.\n\nFound by 0sec automated security-research tooling (https://0sec.ai)."
}
],
"id": "CVE-2026-72091",
"lastModified": "2026-08-17T06:18:08.050",
"metrics": {},
"published": "2026-08-15T06:21:23.180",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/261c1fe3327ad24508f54552c6366e3e4db82c15"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/fff6509d976f6fae423a5236391ccdbd7e0e9f06"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…