Menu

Star on GitHub · 3.2k

CVE-2026-80686

In the Linux kernel, the following vulnerability has been resolved: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE pte_pfn() and pte_dirty() have undefined behaviour when cal…

Published Aug 28, 2026EPSS 0.17%

Overview

CVE-2026-80686 is a known-severity vulnerability. It was published on August 28, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE

pte_pfn() and pte_dirty() have undefined behaviour when called on a

non-present PTE. In migrate_vma_collect_pmd(), these functions may be

invoked on non-present entries (e.g., device-private entries), leading

to potential crashes from pte_pfn() or incorrect dirty folio accounting

from pte_dirty(). Fix both by guarding with pte_present() checks.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80686?

CVE-2026-80686 is a known-severity vulnerability. It was published on August 28, 2026.

How severe is CVE-2026-80686?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80686?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80686?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80686 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.