CVE-2026-72043
Description
A flaw was found in the Linux kernel, specifically affecting the LoongArch architecture when the hardware page table walker (PTW) is enabled. This vulnerability stems from a missing dirty page tracking mechanism in the pte_wrprotect() and pmd_wrprotect() functions, which can lead to incorrect handling of memory pages during copy-on-write operations. As a result, a local user could potentially trigger data corruption, where modified pages are prematurely freed without their contents being properly written back to storage.
Statement
A moderate-impact flaw was found in the Linux kernel on the LoongArch architecture when the hardware page table walker (PTW) is enabled. In this configuration, the CPU may set the _PAGE_DIRTY bit in a page table entry during a write TLB miss without setting the software-only _PAGE_MODIFIED bit, and the copy-on-write write-protection performed by pte_wrprotect() and pmd_wrprotect() during fork()/clone() then clears _PAGE_DIRTY, so the dirtiness information is lost entirely. A local unprivileged user could exploit this behavior by combining madvise(MADV_FREE), write, and fork operations on private anonymous mappings so that, under memory pressure, page reclaim sees modified pages as clean and frees them without writeback, resulting in data corruption. The Red Hat severity of moderate (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) is lower than the upstream CVEORG severity of important (7.1, C:H/I:H/A:N); the two differ primarily in the impact metrics, with Red Hat scoring availability impact only while the CVEORG vector scores confidentiality and integrity. All Red Hat Enterprise Linux and Red Hat In-Vehicle OS kernel and kernel-rt streams are marked not affected for this flaw because the LoongArch-specific vulnerable code is not present in the shipped kernels.
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.1 |
| 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 | None |
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:N
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.