Skip to content
Noroxi
CVE-2025-68321· NVD / CVE Program· CNA Linux

page_pool: always add GFP_NOWARN for ATOMIC allocations

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Dec 16, 2025
Updated
Aug 5, 2026
EPSS
0.4% · 36th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CNA vs NVD score

NVD
—
CNA · Linux
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.18affected
    • ff7d6b27f894f1469dc51ccb828b7363ccd9799f and later · before 0ec2cd5c58793d0c622797cd5fbe26634b357210affected · git
    • ff7d6b27f894f1469dc51ccb828b7363ccd9799f and later · before 9835a0fd59a1df5ec0740fdab6d50db68e0f10deaffected · git
    • ff7d6b27f894f1469dc51ccb828b7363ccd9799f and later · before 7613c06ffa89c1e2266fb532e23ef7dfdf269d73affected · git
    • ff7d6b27f894f1469dc51ccb828b7363ccd9799f and later · before 3671a0775952026228ae44e096eb144bca75f8dcaffected · git
    • ff7d6b27f894f1469dc51ccb828b7363ccd9799f and later · before ab48dc0e23eb714b3f233f8e8f6deed7df2051f5affected · git
    • ff7d6b27f894f1469dc51ccb828b7363ccd9799f and later · before f3b52167a0cb23b27414452fbc1278da2ee884fcaffected · git
    • before 4.18not affected · semver
    • 5.15.197 and later · up to and including 5.15.*not affected · semver
    • 6.1.159 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.8-16.17.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0ec2cd5c58793d0c622797cd5fbe26634b357210Vendor (CNA)
Linux Linux3671a0775952026228ae44e096eb144bca75f8dcVendor (CNA)
Linux Linux7613c06ffa89c1e2266fb532e23ef7dfdf269d73Vendor (CNA)
Linux Linux9835a0fd59a1df5ec0740fdab6d50db68e0f10deVendor (CNA)
Linux Linuxab48dc0e23eb714b3f233f8e8f6deed7df2051f5Vendor (CNA)
Linux Linuxf3b52167a0cb23b27414452fbc1278da2ee884fcVendor (CNA)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records