CVE-2025-68321
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-16

Last updated on: 2025-12-18

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-16
Last Modified
2025-12-18
Generated
2026-06-16
AI Q&A
2025-12-16
EPSS Evaluated
2026-06-14
NVD
CVE-2025-68321
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability relates to the Linux kernel's page pool mechanism where driver authors often forget to add the GFP_NOWARN flag for page allocations made with ATOMIC context. Without GFP_NOWARN, allocation failures during out-of-memory (OOM) conditions can cause unnecessary warnings or issues. The fix ensures that page pool allocations add GFP_NOWARN by default for ATOMIC allocations to avoid these problems.

Impact Analysis

The vulnerability can cause annoying warnings or failures during network receive (Rx) operations when the system is under out-of-memory (OOM) conditions, potentially affecting network performance or stability. By not adding GFP_NOWARN, the system may generate unnecessary warnings that could disrupt normal operation or debugging.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-68321. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart