CVE-2025-68321 json
page_pool: always add GFP_NOWARN for ATOMIC allocations
published 2025-12-16 10 mo ago modified 2026-10-30 9 d ago also EUVD-2025-203809
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.273, 5.15.197, 6.1.159, 6.6.117, 6.12.58, 6.17.8, 6.18
- linux Debian 12 6.1.159-1
- linux Debian 13 6.12.63-1
- linux Debian 14 6.17.8-1
debian advisories DEBIAN-CVE-2025-68321
- linux Ubuntu 22.04 LTS 5.15.0-173.183
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux Ubuntu 25.10 6.17.0-14.14
- linux-aws Ubuntu 22.04 LTS 5.15.0-1103.110
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-aws Ubuntu 25.10 6.17.0-1007.7
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1103.112
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
ubuntu advisories UBUNTU-CVE-2025-68321
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/3c4c2c96d00d112626736cc865b3c75aa8fb6de3 commit
- git.kernel.org/stable/c/0ec2cd5c58793d0c622797cd5fbe26634b357210 commit
- git.kernel.org/stable/c/9835a0fd59a1df5ec0740fdab6d50db68e0f10de commit
- git.kernel.org/stable/c/7613c06ffa89c1e2266fb532e23ef7dfdf269d73 commit
- git.kernel.org/stable/c/3671a0775952026228ae44e096eb144bca75f8dc commit
- git.kernel.org/stable/c/ab48dc0e23eb714b3f233f8e8f6deed7df2051f5 commit
- git.kernel.org/stable/c/f3b52167a0cb23b27414452fbc1278da2ee884fc commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-68321 updated cvss 5.5
kernel: Linux kernel: Denial of Service due to page allocation failures
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 23 d ago
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/3c4c2c96d00d112626736cc865b3c75aa8fb6de3
- git.kernel.org /stable/c/0ec2cd5c58793d0c622797cd5fbe26634b357210
- git.kernel.org /stable/c/9835a0fd59a1df5ec0740fdab6d50db68e0f10de
- git.kernel.org /stable/c/7613c06ffa89c1e2266fb532e23ef7dfdf269d73
- git.kernel.org /stable/c/3671a0775952026228ae44e096eb144bca75f8dc
- git.kernel.org /stable/c/ab48dc0e23eb714b3f233f8e8f6deed7df2051f5
- git.kernel.org /stable/c/f3b52167a0cb23b27414452fbc1278da2ee884fc
Sources
- CVE List CVE-2025-68321
- NVD CVE-2025-68321
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.