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

> A local attacker can trigger a kernel warning and potential crash by exploiting a memory collision in BPF traffic control handling.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2025-68200, DEBIAN-CVE-2025-68200, GHSA-jxw4-crcg-x436, ROOT-OS-DEBIAN-12-CVE-2025-68200, ROOT-OS-DEBIAN-13-CVE-2025-68200, ROOT-OS-UBUNTU-2204-CVE-2025-68200, ROOT-OS-UBUNTU-2404-CVE-2025-68200, UBUNTU-CVE-2025-68200

## What is CVE-2025-68200?

CVE-2025-68200 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-68200?


## How do I fix CVE-2025-68200?

Apply the vendor's patch.

## Is CVE-2025-68200 being exploited?

There is no known exploitation of CVE-2025-68200 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68200 and fix it if it is affected.

What it is: CVE-2025-68200 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68200 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68200/ (Markdown: https://insights.sbomify.com/CVE-2025-68200/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68200
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68200
- OSV: https://osv.dev/vulnerability/CVE-2025-68200

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68200/
Summaries are generated and may contain mistakes; the official description above is the record.