Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers()

Noroxi assessment

Priority: Monitor (action score 0/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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 4ef92743625818932b9c320152b58274c05e5053, 5.15.197, 5e149d8a8e732126fb6014efd60075cf63a73f91.

Low priority for now. Upgrade to Linux Linux 4ef92743625818932b9c320152b58274c05e5053, 5.15.197, 5e149d8a8e732126fb6014efd60075cf63a73f91 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: Add bpf_prog_run_data_pointers() syzbot found that cls_bpf_classify() is able to change tc_skb_cb(skb)->drop_reason triggering a warning in sk_skb_reason_drop(). WARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline] WARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214 struct tc_skb_cb has been added in commit ec624fe740b4 ("net/sched: Extend qdisc control block with tc control block"), which added a wrong interaction with db58ba459202 ("bpf: wire in data and data_end for cls_act_bpf"). drop_reason was added later. Add bpf_prog_run_data_pointers() helper to save/restore the net_sched storage colliding with BPF data_meta/data_end.

—No exploit Fix available
Published
Dec 16, 2025
Updated
Oct 14, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-68200

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

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.

—

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.16affected
    • 0d76daf2013ce1da20eab5e26bd81d983e1c18fb and later · before c4cdd143c35974a2cedd000fa9eb3accc3023b20affected · git
    • ec624fe740b416fb68d536b37fb8eef46f90b5c2 and later · before 5e149d8a8e732126fb6014efd60075cf63a73f91affected · git
    • ec624fe740b416fb68d536b37fb8eef46f90b5c2 and later · before baa61dcaa50b7141048c8d2aede7fe9ed8f21d11affected · git
    • ec624fe740b416fb68d536b37fb8eef46f90b5c2 and later · before 6392e5f4b1a3cce10e828309baf35d22abd3457daffected · git
    • ec624fe740b416fb68d536b37fb8eef46f90b5c2 and later · before 8dd2fe5f5d586c8e87307b7a271f6b994afcc006affected · git
    • ec624fe740b416fb68d536b37fb8eef46f90b5c2 and later · before 4ef92743625818932b9c320152b58274c05e5053affected · git
    • 5.15.13 and later · before 5.15.197affected · semver
    • before 5.16not affected · semver
    • 5.15.197 and later · up to and including 5.15.*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.9-16.17.9-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

Published before and after this one in the same product

  • ← EarlierCVE-2025-68198Dec 16, 2025 · crash: fix crashkernel resource shrink
    0Monitor
  • ← EarlierCVE-2025-68199Dec 16, 2025 · codetag: debug: handle existing CODETAG_EMPTY in mark_objexts_empty for slabobj_ext
    0Monitor
  • Later →CVE-2025-68201Dec 16, 2025 · drm/amdgpu: remove two invalid BUG_ON()s
    0Monitor

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 Linux4ef92743625818932b9c320152b58274c05e5053Vendor (CNA)
Linux Linux5.15.197Vendor (CNA)
Linux Linux5e149d8a8e732126fb6014efd60075cf63a73f91Vendor (CNA)
Linux Linux6392e5f4b1a3cce10e828309baf35d22abd3457dVendor (CNA)
Linux Linux8dd2fe5f5d586c8e87307b7a271f6b994afcc006Vendor (CNA)
Linux Linuxbaa61dcaa50b7141048c8d2aede7fe9ed8f21d11Vendor (CNA)
Linux Linuxc4cdd143c35974a2cedd000fa9eb3accc3023b20Vendor (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.

No history yet (it accumulates with the daily EPSS job).

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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