{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80657 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80657 is a vulnerability in Linux, published on 28 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-80657 and fix it if it is affected.\n\nWhat it is: CVE-2026-80657 is a vulnerability in Linux, published on 28 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-80657 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-80657/ (Markdown: https://insights.sbomify.com/CVE-2026-80657/index.md)","id":"CVE-2026-80657","markdown":"https://insights.sbomify.com/CVE-2026-80657/index.md","name":"CVE-2026-80657","record":{"aliases":["BELL-CVE-2026-80657","DEBIAN-CVE-2026-80657","GHSA-hwpp-gg7q-6q46","UBUNTU-CVE-2026-80657"],"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 can cause a denial of service in the Linux kernel by triggering a NULL pointer dereference in the AMD XDNA driver cleanup path.","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: Guard management mailbox channel cleanup against NULL pointer\n\nThe management mailbox channel cleanup helpers can be called from\nerror handling paths when mgmt_chann has already been destroyed.\n\nAdd NULL checks to xdna_mailbox_free_channel() and\nxdna_mailbox_stop_channel() so the cleanup path safely returns instead\nof dereferencing a NULL mailbox channel pointer.","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: Guard management mailbox channel cleanup against NULL pointer","id":"CVE-2026-80657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"drm/rockchip: dw_dp: Fix null-ptr-deref in dw_dp_remove()","id":"CVE-2026-80658"},"packages":[],"prev":{"headline":"hfsplus: Add a sanity check for btree node size","id":"CVE-2026-80656"},"products":["Linux"],"published":"2026-08-28","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-08-28","vendors":["Linux"]},"summary":"A local attacker can cause a denial of service in the Linux kernel by triggering a NULL pointer dereference in the AMD XDNA driver cleanup path.","url":"https://insights.sbomify.com/CVE-2026-80657/"}