{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72091 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72091 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72091 and fix it if it is affected.\n\nWhat it is: CVE-2026-72091 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72091 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72091/ (Markdown: https://insights.sbomify.com/CVE-2026-72091/index.md)","id":"CVE-2026-72091","markdown":"https://insights.sbomify.com/CVE-2026-72091/index.md","name":"CVE-2026-72091","record":{"aliases":["BELL-CVE-2026-72091","DEBIAN-CVE-2026-72091","GHSA-jvc7-qr5g-mx5f","UBUNTU-CVE-2026-72091"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker with access to the AMD NPU device node can trigger a kernel null pointer dereference, causing a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"accel/amdxdna: reject user command submission without a command BO","id":"CVE-2026-72091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"accel/amdxdna: reject command submission on devices without a submit op","id":"CVE-2026-72092"},"packages":[],"prev":{"headline":"accel/amdxdna: Use caller client for debug BO sync","id":"CVE-2026-72090"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A local attacker with access to the AMD NPU device node can trigger a kernel null pointer dereference, causing a system crash.","url":"https://insights.sbomify.com/CVE-2026-72091/"}