{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80686 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80686 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-80686 and fix it if it is affected.\n\nWhat it is: CVE-2026-80686 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-80686 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-80686/ (Markdown: https://insights.sbomify.com/CVE-2026-80686/index.md)","id":"CVE-2026-80686","markdown":"https://insights.sbomify.com/CVE-2026-80686/index.md","name":"CVE-2026-80686","record":{"aliases":["AZL-98147","BELL-CVE-2026-80686","DEBIAN-CVE-2026-80686","GHSA-m9fp-2x7c-5r66","UBUNTU-CVE-2026-80686"],"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":"none","summary":"A local attacker can trigger a kernel crash or incorrect memory accounting by exploiting undefined behavior in device memory migration code.","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\nmm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE\n\npte_pfn() and pte_dirty() have undefined behaviour when called on a\nnon-present PTE. In migrate_vma_collect_pmd(), these functions may be\ninvoked on non-present entries (e.g., device-private entries), leading\nto potential crashes from pte_pfn() or incorrect dirty folio accounting\nfrom pte_dirty(). Fix both by guarding with pte_present() checks.","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":"mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE","id":"CVE-2026-80686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"iommufd/viommu: Release the igroup lock on the vdevice_size error path","id":"CVE-2026-80687"},"packages":[],"prev":{"headline":"mm/util: don't read __page_2 for order-1 folios in snapshot_page()","id":"CVE-2026-80685"},"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 trigger a kernel crash or incorrect memory accounting by exploiting undefined behavior in device memory migration code.","url":"https://insights.sbomify.com/CVE-2026-80686/"}