Skip to main content
Mallory
HighVulnerability

CVE-2025-38201: Linux kernel nft_set_pipapo oversized map bucket kernel warning

Published Jul 4, 2025 · Updated 7 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.24%15th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Linux
IdentifiersCVE-2025-38201CWE-1284

CVE-2025-38201 is a size-validation vulnerability in the Linux kernel's netfilter nft_set_pipapo implementation. The maximum map bucket size is insufficiently bounded, allowing hash-table resizing to request an oversized allocation and trigger WARN_ON_ONCE in __kvmalloc_node_noprof() because __GFP_NOWARN is unset. The fix clamps the maximum map bucket size to INT_MAX. The issue primarily concerns local availability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Triggering the condition produces a kernel warning during hash-table resizing. SUSE assesses the vulnerability as a local denial-of-service issue with high availability impact and no confidentiality or integrity impact. Although other assessments assign broader impacts, the documented mechanism does not establish arbitrary code execution, privilege escalation, or information disclosure.

Mitigation

If you can’t patch tonight, do this now.

Until patched, limit or avoid nftables configurations using nft_set_pipapo maps that can reach oversized bucket allocations during resizing. Restrict untrusted users and containers from managing nftables rulesets, including unnecessary CAP_NET_ADMIN privileges. These controls reduce exposure but do not replace the kernel update.

Remediation

Patch, then assume compromise.

Install a vendor-supported kernel update containing the nft_set_pipapo fix that clamps maximum map bucket size to INT_MAX, then reboot into the updated kernel. Fixed package examples include kernel-default 6.4.0-150600.23.70.1 for SLES 15 SP6 and openSUSE Leap 15.6, 6.4.0-150700.53.16.1 for SLES 15 SP7, and 6.4.0-34.1 for SUSE Linux Micro 6.0/6.1. Echo lists linux 6.1.164-1 or later; Google COS lists the applicable kernel package update at 18613.534.35 or later. Tanzu Ubuntu Jammy stemcell fixes are included in release 1.1282.x. Select the update for the exact product and kernel flavor; an initial livepatch infrastructure package alone may not contain the fix.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2025-38201 exploited in the wild?
As of Nov 10, 2026, Mallory has no reports of CVE-2025-38201 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-38201?
As of Nov 10, 2026, Mallory has found no public exploit for CVE-2025-38201.
Is there a patch for CVE-2025-38201?
Install a vendor-supported kernel update containing the nft_set_pipapo fix that clamps maximum map bucket size to INT_MAX, then reboot into the updated kernel. Fixed package examples include kernel-default 6.4.0-150600.23.70.1 for SLES 15 SP6 and openSUSE Leap 15.6, 6.4.0-150700.53.16.1 for SLES 15 SP7, and 6.4.0-34.1 for SUSE Linux Micro 6.0/6.1.
What products are affected by CVE-2025-38201?
Linux Kernel.
How severe is CVE-2025-38201?
CVE-2025-38201 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.24% (15th percentile) as of Nov 10, 2026.
Activity feed

Recent activity

25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.