CVE-2026-80682
Description
A flaw was found in the Linux kernel's RISC-V memory management component. An incorrect calculation for memory alignment during system initialization could lead to a kernel warning. This issue arises when the physical memory base address is not properly aligned, potentially causing system instability or a denial of service (DoS) on affected RISC-V systems.
Statement
A moderate-impact flaw was found in the Linux kernel's RISC-V memory management code. When computing the start of the vmemmap region, the kernel rounds the physical RAM base address down to an alignment boundary, but a recent upstream change fed an alignment value measured in bytes of struct page storage (MAX_FOLIO_VMEMMAP_ALIGN) directly into a macro that expects a physical-address alignment. On RISC-V systems whose DRAM base address is not aligned to MAX_FOLIO_NR_PAGES * PAGE_SIZE, such as QEMU virt, this unit mismatch triggers a kernel WARNING in sparse_init() during early boot, which can cause system instability or a denial of service. The flaw affects only availability; there is no impact on confidentiality or integrity. Red Hat Product Security rates this flaw Moderate severity with a CVSS 3.1 base score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which is lower than the CVEORG score of 7.8 because the issue only affects system availability. The vulnerable code was introduced in recent upstream kernel development and is not present in Red Hat's shipped kernels: the Red Hat Enterprise Linux and Red Hat In-Vehicle OS kernel and kernel-rt components listed for this CVE are marked not affected (vulnerable code not present), so no changes to Red Hat products are required.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
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:H/A:H
Understanding the Weakness (CWE)
Integrity,Availability,Confidentiality
Technical Impact: DoS: Crash, Exit, or Restart; Execute Unauthorized Code or Commands; Read Memory; Modify Memory
If the incorrect calculation is used in the context of memory allocation, then the software may create a buffer that is smaller or larger than expected. If the allocated buffer is smaller than expected, this could lead to an out-of-bounds read or write (CWE-119), possibly causing a crash, allowing arbitrary code execution, or exposing sensitive data.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.