CVE-2026-97533
Description
A flaw was found in the Linux kernel's x86 Page Attribute Table (PAT) memory management subsystem. A race condition occurs when memory attributes are changed concurrently with page table collapse operations, allowing the kernel to access memory after it has been freed. A local user could exploit this use-after-free vulnerability to potentially escalate privileges or crash the system, resulting in a Denial of Service (DoS).
Statement
A race between a lockless CPA page table walk and concurrent CPA collapse can free the page table that contains a previously obtained PTE. A later set_pte_atomic call can then write through the stale PTE pointer, resulting in a use after free write and possible corruption of reused kernel memory. Reliable triggering requires winning a timing window, therefore AC:H is appropriate. For the CVSS the PR:L value is used for the paranoid case because a local user may be able to trigger module autoload or another kernel operation that indirectly reaches the relevant CPA paths without full administrative control. The base case uses PR:H because direct control of module mapping and memory attribute changes is normally privileged. The issue is not directly network reachable. Impact is at least a local denial of service through memory corruption and a kernel crash.
Mitigation
Mitigation for this issue is either not available or the currently available options don't 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 | 7 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | 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 | High | N/A | N/A |
| Integrity Impact | High | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.