CVE-2025-68378
What it is
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stackmap overflow check in __bpf_get_stackid() Syzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid() when copying stack trace data. The issue occurs when the perf trace contains more stack entries than the stack map bucket can hold, leading to an out-of-bounds write in the bucket's data array.
At a glance
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Deferred
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-68378.md and follow it. Check whether this project is affected by CVE-2025-68378. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/03fe4c886667b3a09b9d6afc03bbc68afb35c82b
- https://git.kernel.org/stable/c/23f852daa4bab4d579110e034e4d513f7d490846
- https://git.kernel.org/stable/c/2a008f6de163279deffd488c1deab081bce5667c
- https://git.kernel.org/stable/c/4669a8db976c8cbd5427fe9945f12c5fa5168ff3
- https://git.kernel.org/stable/c/d1f424a77b6bd27b361737ed73df49a0158f1590
- https://git.kernel.org/stable/c/d6028caa0ee39dccd005468adfa3223b92bd3ad3