{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80884 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80884 is a memory corruption vulnerability in Linux, published on 4 Sep 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-80884 and fix it if it is affected.\n\nWhat it is: CVE-2026-80884 is a memory corruption vulnerability in Linux, published on 4 Sep 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-80884 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-80884/ (Markdown: https://insights.sbomify.com/CVE-2026-80884/index.md)","id":"CVE-2026-80884","markdown":"https://insights.sbomify.com/CVE-2026-80884/index.md","name":"CVE-2026-80884","record":{"aliases":["AZL-99626","BELL-CVE-2026-80884","DEBIAN-CVE-2026-80884","GHSA-44m4-vqfj-mwrf","UBUNTU-CVE-2026-80884"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A Linux kernel bug in the NTB driver mishandles DMA addresses, potentially causing memory corruption or crashes when releasing resources.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nntb: Store original DMA address for future release\n\nThe DMA API requires that dma_free_attrs receive the exact dma_handle\noriginally returned by the allocation function. Do not modify it.","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":"ntb: Store original DMA address for future release","id":"CVE-2026-80884","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"afs: Fix uncancelled rxrpc OOB message handler","id":"CVE-2026-80885"},"packages":[],"prev":{"headline":"drm/tegra: gr2d/gr3d: Initialize address register map before HOST1X client is registered","id":"CVE-2026-80883"},"products":["Linux"],"published":"2026-09-04","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-21","vendors":["Linux"]},"summary":"A Linux kernel bug in the NTB driver mishandles DMA addresses, potentially causing memory corruption or crashes when releasing resources.","url":"https://insights.sbomify.com/CVE-2026-80884/"}