{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72090 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72090 is a high-severity 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-72090 and fix it if it is affected.\n\nWhat it is: CVE-2026-72090 is a high-severity 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-72090 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-72090/ (Markdown: https://insights.sbomify.com/CVE-2026-72090/index.md)","id":"CVE-2026-72090","markdown":"https://insights.sbomify.com/CVE-2026-72090/index.md","name":"CVE-2026-72090","record":{"aliases":["DEBIAN-CVE-2026-72090","GHSA-qqcm-w5c8-f3qv","UBUNTU-CVE-2026-72090"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"Incorrect client context usage in AMD XDNA driver debug buffer sync may cause logic errors or undefined behavior in kernel space.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/amdxdna: Use caller client for debug BO sync\n\namdxdna_drm_sync_bo_ioctl() looks up args-\u003ehandle in the ioctl caller's\ndrm_file. For SYNC_DIRECT_FROM_DEVICE, it then calls\namdxdna_hwctx_sync_debug_bo(), but passes abo-\u003eclient.\n\namdxdna_hwctx_sync_debug_bo() uses the passed client both as the handle\nnamespace for debug_bo_hdl and as the owner of the hardware context xarray.\nThose must match the file that supplied args-\u003ehandle. The BO's stored\nclient pointer is object state, not the ioctl context.\n\nPass filp-\u003edriver_priv instead, matching the original handle lookup.","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: Use caller client for debug BO sync","id":"CVE-2026-72090","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"accel/amdxdna: reject user command submission without a command BO","id":"CVE-2026-72091"},"packages":[],"prev":{"headline":"accel/ivpu: Reject firmware log with size smaller than header","id":"CVE-2026-72089"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"Incorrect client context usage in AMD XDNA driver debug buffer sync may cause logic errors or undefined behavior in kernel space.","url":"https://insights.sbomify.com/CVE-2026-72090/"}