CVE-2026-99654
Description
A flaw was found in the Linux kernel's memory management subsystem. On 32-bit systems, an integer truncation issue occurs when handling memory unmapping operations for file offsets exceeding four gigabytes. A local user manipulating large file mappings can cause the kernel to unmap unintended memory regions instead of the requested range. This can lead to data loss or data corruption in affected private memory mappings.
Statement
This vulnerability is rated as Moderate impact because exploitation requires authenticated local access to induce data integrity issues and is strictly limited to 32-bit kernel architectures. Standard Red Hat Enterprise Linux deployments utilize 64-bit kernels where address types retain sufficient width, natively preventing this truncation behavior and leaving standard enterprise installations unaffected. In 32-bit deployments, risk is constrained to local users truncating or unmapping large file mappings that exceed four gigabytes.
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 | 4.4 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | Low | N/A | N/A |
| Availability Impact | Low | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Understanding the Weakness (CWE)
Other,Integrity
Technical Impact: Unexpected State; Quality Degradation
The program could wind up using the wrong number and generate incorrect results. If the number is used to allocate resources or make a security decision, then this could introduce a vulnerability.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.