Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-68200bpf: Add bpf_prog_run_data_pointers()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 0d76daf2013ce1da20eab5e26bd81d983e1c18fb – < c4cdd143c35974a2cedd000fa9eb3accc3023b20
    • affected ec624fe740b416fb68d536b37fb8eef46f90b5c2 – < 5e149d8a8e732126fb6014efd60075cf63a73f91
    • affected ec624fe740b416fb68d536b37fb8eef46f90b5c2 – < baa61dcaa50b7141048c8d2aede7fe9ed8f21d11
    • affected ec624fe740b416fb68d536b37fb8eef46f90b5c2 – < 6392e5f4b1a3cce10e828309baf35d22abd3457d
    • affected ec624fe740b416fb68d536b37fb8eef46f90b5c2 – < 8dd2fe5f5d586c8e87307b7a271f6b994afcc006
    • affected ec624fe740b416fb68d536b37fb8eef46f90b5c2 – < 4ef92743625818932b9c320152b58274c05e5053
    • affected 5.15.13 – < 5.15.197
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 5.15.197 – ≤ 5.15.*
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.117 – ≤ 6.6.*
    • unaffected 6.12.59 – ≤ 6.12.*
    • unaffected 6.17.9 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68200 badge
[![CVE-2025-68200](https://cveledger.app/badge/CVE-2025-68200.svg)](https://cveledger.app/cve/CVE-2025-68200)

Record last updated .