CVE-2025-68321: Linux kernel · page_pool: always add GFP_NOWARN for ATOMIC allocations
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in f3b52167a0cb23b27414452fbc1278da2ee884fc : patch Linux kernel soon.
Data as of 30 Oct 2026, 12:49 UTC
Thin evidence
One scorer or none| CNA (Linux) | CVSS 3.1 | 7.5 |
|---|
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in f3b52167a0cb23b27414452fbc1278da2ee884fc, ab48dc0e23eb714b3f233f8e8f6deed7df2051f5, 9835a0fd59a1df5ec0740fdab6d50db68e0f10de +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to the fixed versions identified by the provided commit hashes to remediate this issue.
Description
CVE-2025-68321 is a high-severity vulnerability in the Linux kernel affecting version 4.18. It involves the page_pool subsystem where GFP_NOWARN was not added for ATOMIC allocations, causing unnecessary warnings during out-of-memory (OOM) conditions. The issue has been fixed by ensuring GFP_NOWARN is added by default for these allocations.
References
- git.kernel.org/stable/c/3c4c2c96d00d112626736cc865b3c75aa8fb6de3 (opens in a new tab)
- git.kernel.org/stable/c/0ec2cd5c58793d0c622797cd5fbe26634b357210 (opens in a new tab)
- git.kernel.org/stable/c/9835a0fd59a1df5ec0740fdab6d50db68e0f10de (opens in a new tab)
- git.kernel.org/stable/c/7613c06ffa89c1e2266fb532e23ef7dfdf269d73 (opens in a new tab)
- git.kernel.org/stable/c/3671a0775952026228ae44e096eb144bca75f8dc (opens in a new tab)
- git.kernel.org/stable/c/ab48dc0e23eb714b3f233f8e8f6deed7df2051f5 (opens in a new tab)
- git.kernel.org/stable/c/f3b52167a0cb23b27414452fbc1278da2ee884fc (opens in a new tab)