CVE-2026-80686

Description

A flaw was found in the Linux kernel's memory management component. Specifically, the migrate_device functionality may attempt to access memory page table entries (PTEs) that are not present. This incorrect handling can lead to system instability, potentially causing a system crash (Denial of Service) or inaccurate accounting of modified memory pages.

Statement

A moderate impact flaw was found in the Linux kernel's migrate_device memory management code, affecting the kernel and kernel-rt components shipped in Red Hat Enterprise Linux 9 and 10 and in Red Hat In-Vehicle OS 2. In migrate_vma_collect_pmd(), pte_pfn() and pte_dirty() may be invoked on non-present page table entries, such as device-private entries, for which these operations are undefined. A local user able to exercise a driver or device path that invokes migrate_vma() on a system using device-private memory could exploit this behavior to crash the kernel, causing a denial of service, or to trigger incorrect dirty folio accounting. Red Hat assesses the impact of this flaw as Moderate (CVSS 3.1 score 5.5, vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), with no impact on confidentiality or integrity. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those versions; the change that introduced this flaw first appears in Red Hat Enterprise Linux 9 streams. For the affected Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, and Red Hat In-Vehicle OS 2 streams, the fix is currently deferred because triggering the flaw requires specific local conditions, namely a locally running process must drive device-private page migration, and the residual risk is limited to local denial of service or inaccurate memory accounting rather than loss of confidentiality or integrity. The fix will be delivered through a future kernel update.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the uninitialized pointer is used in a read operation, it might not point to a valid memory location. An attacker might be able to read sensitive portions of memory.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the uninitialized pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the uninitialized pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked.

Frequently Asked Questions

Want to get errata notifications? Sign up here.