Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68725: bpf: Do not let BPF test infra emit invalid GSO types to stack

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 04a899573fb87273a656f178b5f920c505f68875, 0f3a60869ca22024dfb9c6fce412b0c70cb4ea36, 768376ece7036ecb8604961793a1b72afe6345dd; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.126.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.

Low priority for now. Upgrade to Linux Linux 04a899573fb87273a656f178b5f920c505f68875, 0f3a60869ca22024dfb9c6fce412b0c70cb4ea36, 768376ece7036ecb8604961793a1b72afe6345dd; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.126.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: bpf: Do not let BPF test infra emit invalid GSO types to stack Yinhao et al. reported that their fuzzer tool was able to trigger a skb_warn_bad_offload() from netif_skb_features() -> gso_features_check(). When a BPF program - triggered via BPF test infra - pushes the packet to the loopback device via bpf_clone_redirect() then mentioned offload warning can be seen. GSO-related features are then rightfully disabled. We get into this situation due to convert___skb_to_skb() setting gso_segs and gso_size but not gso_type. Technically, it makes sense that this warning triggers since the GSO properties are malformed due to the gso_type. Potentially, the gso_type could be marked non-trustworthy through setting it at least to SKB_GSO_DODGY without any other specific assumptions, but that also feels wrong given we should not go further into the GSO engine in the first place. The checks were added in 121d57af308d ("gso: validate gso_type in GSO handlers") because there were malicious (syzbot) senders that combine a protocol with a non-matching gso_type. If we would want to drop such packets, gso_features_check() currently only returns feature flags via netif_skb_features(), so one location for potentially dropping such skbs could be validate_xmit_unreadable_skb(), but then otoh it would be an additional check in the fast-path for a very corner case. Given bpf_clone_redirect() is the only place where BPF test infra could emit such packets, lets reject them right there.

Published
Dec 24, 2025
Updated
Nov 10, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68725

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

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

    • 5.6affected
    • 850a88cc4096fe1df407452ba2e4d28cf5b3eee9 and later · before bb7902ed7d7f6d6a7c6c4dc25410d6127ce1085faffected · git
    • 850a88cc4096fe1df407452ba2e4d28cf5b3eee9 and later · before e0ffb64a2d72c6705b4a4c9efef600409f7e98a0affected · git
    • 850a88cc4096fe1df407452ba2e4d28cf5b3eee9 and later · before 768376ece7036ecb8604961793a1b72afe6345ddaffected · git
    • 850a88cc4096fe1df407452ba2e4d28cf5b3eee9 and later · before 8670b53b8ee91f028f7240531064020b7413c461affected · git
    • 850a88cc4096fe1df407452ba2e4d28cf5b3eee9 and later · before 0f3a60869ca22024dfb9c6fce412b0c70cb4ea36affected · git
    • 850a88cc4096fe1df407452ba2e4d28cf5b3eee9 and later · before fbea4c63b5385588cb44ab21f91e55e33c719a54affected · git
    • 850a88cc4096fe1df407452ba2e4d28cf5b3eee9 and later · before 04a899573fb87273a656f178b5f920c505f68875affected · git
    • before 5.6not affected · semver
    • 5.10.249 and later · up to and including 5.10.*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.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-68351Dec 24, 2025 · exfat: fix refcount leak in exfat_find
    22Monitor
  • ← EarlierCVE-2025-68365Dec 24, 2025 · fs/ntfs3: Initialize allocated memory before use
    22Monitor
  • Later →CVE-2025-68749Dec 24, 2025 · accel/ivpu: Fix race condition when unbinding BOs
    18Monitor

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 Linux04a899573fb87273a656f178b5f920c505f68875Vendor (CNA)
Linux Linux0f3a60869ca22024dfb9c6fce412b0c70cb4ea36Vendor (CNA)
Linux Linux768376ece7036ecb8604961793a1b72afe6345ddVendor (CNA)
Linux Linux8670b53b8ee91f028f7240531064020b7413c461Vendor (CNA)
Linux Linuxbb7902ed7d7f6d6a7c6c4dc25410d6127ce1085fVendor (CNA)
Linux Linuxe0ffb64a2d72c6705b4a4c9efef600409f7e98a0Vendor (CNA)
Linux Linuxfbea4c63b5385588cb44ab21f91e55e33c719a54Vendor (CNA)
azl3 kernel 6.6.121.1-1 on Azure Linux 3.06.6.126.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.162-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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • 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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

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.

References

All records