CVE-2025-68321
Description
In the Linux kernel, the following vulnerability has been resolved:
page_pool: always add GFP_NOWARN for ATOMIC allocations
Driver authors often forget to add GFP_NOWARN for page allocation from the datapath. This is annoying to users as OOMs are a fact of life, and we pretty much expect network Rx to hit page allocation failures during OOM. Make page pool add GFP_NOWARN for ATOMIC allocations by default.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
The Linux kernel's page_pool now automatically adds GFP_NOWARN for atomic allocations to suppress unwanted OOM warnings during network Rx.
Description
CVE-2025-68321 addresses a quality-of-life issue in the Linux kernel's page_pool subsystem. The root cause is that driver authors frequently neglected to add the GFP_NOWARN flag for atomic page allocations performed in the network data path. During out-of-memory (OOM) conditions, these allocations would trigger verbose kernel warnings, which are considered annoying and unhelpful to users because network receive (Rx) failures during OOM are a normal, expected behavior.
Exploitation
Context
This is not a security vulnerability in the traditional sense; it is a defect that causes excessive kernel logging. The attack surface is the system's memory pressure. When the system is under OOM conditions, page allocation requests from the network datapath (which are atomic, i.e., cannot sleep) would fail, and the kernel would print warnings. No authentication or network position is required; the condition is triggered by normal network activity during memory stress.
Impact
An attacker able to induce OOM conditions on a target system could cause a flood of kernel warning messages. While this does not directly compromise confidentiality, integrity, or availability, the log spam could obscure other malicious activity or consume system resources. The primary impact is on system monitoring and log management.
Mitigation
The fix ensures that the page_pool automatically adds GFP_NOWARN when performing atomic allocations, silencing the warnings [1][2][3][4]. The patch has been accepted into the stable kernel trees and is available through the referenced commits. Users should apply the corresponding stable kernel update to receive the fix.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
6- git.kernel.org/stable/c/0ec2cd5c58793d0c622797cd5fbe26634b357210nvd
- git.kernel.org/stable/c/3671a0775952026228ae44e096eb144bca75f8dcnvd
- git.kernel.org/stable/c/7613c06ffa89c1e2266fb532e23ef7dfdf269d73nvd
- git.kernel.org/stable/c/9835a0fd59a1df5ec0740fdab6d50db68e0f10denvd
- git.kernel.org/stable/c/ab48dc0e23eb714b3f233f8e8f6deed7df2051f5nvd
- git.kernel.org/stable/c/f3b52167a0cb23b27414452fbc1278da2ee884fcnvd
News mentions
0No linked articles in our index yet.