{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80894 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80894 is a 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-80894 and fix it if it is affected.\n\nWhat it is: CVE-2026-80894 is a 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-80894 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-80894/ (Markdown: https://insights.sbomify.com/CVE-2026-80894/index.md)","id":"CVE-2026-80894","markdown":"https://insights.sbomify.com/CVE-2026-80894/index.md","name":"CVE-2026-80894","record":{"aliases":["BELL-CVE-2026-80894","DEBIAN-CVE-2026-80894","GHSA-jg86-gjjj-22qv","UBUNTU-CVE-2026-80894"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A logic error in the Linux kernel iommufd subsystem causes incorrect fault handling during device replacement, potentially leading to denial of service.","user_interaction":"not_required","vuln_class":"other"},"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\niommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace\n\niommufd_hwpt_replace_device() calls:\n\n\tiommufd_auto_response_faults(hwpt, old_handle);\n\npassing the *new* hwpt together with the handle of\nthe device's *old* domain. This should be a parameter mismatch:\n\n1. Semantically, iommufd_auto_response_faults(x, handle) scans\n   x-\u003efault's deliver list and response xarray for groups matching\n   \"handle\". A group is queued under the hwpt that was attached at\n   fault-delivery time. old_handle is fetched *before* the domain switch,\n   so its group lives on old-\u003efault, not on the new hwpt-\u003efault.\n\n2. Historically, the first argument was \"old\". The routine was\n   introduced by commit b7d8833677ba (\"iommufd: Fault-capable hwpt\n   attach/detach/replace\") as __fault_domain_replace_dev() in\n   fault.c, correctly calling iommufd_auto_response_faults(old, curr).\n   Commit fb21b1568ada (\"iommufd: Make attach_handle generic than\n   fault specific\") moved this into iommufd_hwpt_replace_device() in\n   device.c and swapped it to \"hwpt\". This should be a refactor regression,\n   not an intentional change.\n\nFix this by passing \"old\" instead.","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":"iommufd: Fix wrong hwpt passed to iommufd_auto_response_faults on replace","id":"CVE-2026-80894","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"mshv: Order pt_vp_array publish against irqfd assertion path","id":"CVE-2026-80895"},"packages":[],"prev":{"headline":"mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork()","id":"CVE-2026-80893"},"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-09-04","vendors":["Linux"]},"summary":"A logic error in the Linux kernel iommufd subsystem causes incorrect fault handling during device replacement, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-80894/"}