CVE-2026-80685

Description

A flaw was found in the Linux kernel's memory management subsystem. The snapshot_page() function attempts to read memory that may not exist when handling certain memory structures (order-1 folios) during specific memory operations, such as dynamic logical partitioning (DLPAR) memory removal. This out-of-bounds read can lead to a kernel fault (oops), resulting in a system crash and a Denial of Service (DoS).

Statement

An out-of-bounds read flaw rated LOW impact by Red Hat was found in the Linux kernel's memory management subsystem. The snapshot_page() function in mm/util reads __page_2 after only checking that a folio spans more than one page, but __page_2 exists only when a folio spans more than two pages. When an order-1 folio is allocated at the end of a vmemmap section, the read accesses memmap that does not exist (an adjacent absent, unmapped vmemmap section) and causes a kernel fault (oops). The issue was observed on the page isolation path during DLPAR memory removal on a large ppc64le LPAR, so triggering it requires privileged local memory-reconfiguration operations such as DLPAR memory remove or memory hotplug; the consequence is a system crash resulting in denial of service, with no confidentiality or integrity impact because the read causes a fault rather than a controlled disclosure. For this reason Red Hat's severity (CVSS 5.5, Moderate, LOW impact) is lower than the upstream CVEORG score (7.1, Important), which credits a high confidentiality impact. Of the currently tracked Red Hat product streams, the Red Hat Enterprise Linux and Red Hat In-Vehicle OS kernel and kernel-rt streams are not affected because the vulnerable code is not present in them; the one remaining flagged stream (the rhel-6-els kernel) is out of support scope.

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/A7.1
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

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

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.