CVE-2026-90201
Description
A flaw was found in the Linux kernel's page_pool networking component. A race condition can occur when the page_pool_destroy() function runs concurrently with page return operations. This race condition can lead to a Use-After-Free (UAF) vulnerability, where the system attempts to access memory after it has been freed. This could potentially allow an attacker to cause a denial of service or execute arbitrary code.
Statement
A race in net page_pool DMA cleanup can cause a use-after-free when page_pool_destroy() runs page_pool_scrub() while another CPU returns a page through page_pool_put_netmem(). The scrub path iterates pool dma_mapped without holding a page reference, while the return path can drop the last page reference after losing xa_cmpxchg. This allows the scrub path to read or update netmem fields after the page has been freed. For the CVSS the PR:L is used in the paranoid score because reliable triggering may be possible for a local actor with delegated CAP_NET_ADMIN or similar control over NIC channel or ring reconfiguration. The issue is not directly network reachable by packets alone, but traffic such as iperf style load can help exercise the race while local reconfiguration is performed. Impact is at least denial of service via kernel crash and in worst case may allow confidentiality or integrity impact due to UAF based memory corruption.
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 | 4.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 | None | N/A | N/A |
| Integrity Impact | None | 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:N/I:N/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.