Kernel warning via BPF control-block collision
Published Dec 16, 2025 · Updated Dec 16, 2025
Improper BPF state handling in Linux allows local users to trigger a kernel warning through a traffic-control BPF classifier. cls_bpf_classify() lets BPF data_meta and data_end overwrite shared net_sched control-block storage, including drop_reason, because that storage is not preserved around program execution. Reaching the classifier requires privileged BPF and traffic-control access, and the documented consequence is a warning rather than a crash.
Summary
What happened
Improper BPF state handling in Linux allows local users to trigger a kernel warning through a traffic-control BPF classifier. cls_bpf_classify() lets BPF data_meta and data_end overwrite shared net_sched control-block storage, including drop_reason, because that storage is not preserved around program execution. Reaching the classifier requires privileged BPF and traffic-control access, and the documented consequence is a warning rather than a crash.
The record
- CVE
- CVE-2025-68200
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0d76daf2013ce1da20eab5e26bd81d983e1c18fb <c4cdd143c35974a2cedd000fa9eb3accc3023b20
- Affected versionversion=5.16
- Affected versionversion=ec624fe740b416fb68d536b37fb8eef46f90b5c2 <4ef92743625818932b9c320152b58274c05e5053
- Affected versionversion=ec624fe740b416fb68d536b37fb8eef46f90b5c2 <5e149d8a8e732126fb6014efd60075cf63a73f91
- Affected versionversion=ec624fe740b416fb68d536b37fb8eef46f90b5c2 <6392e5f4b1a3cce10e828309baf35d22abd3457d
- Affected versionversion=ec624fe740b416fb68d536b37fb8eef46f90b5c2 <8dd2fe5f5d586c8e87307b7a271f6b994afcc006
- Affected versionversion=ec624fe740b416fb68d536b37fb8eef46f90b5c2 <baa61dcaa50b7141048c8d2aede7fe9ed8f21d11
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo