bpf: Fix stackmap overflow check in __bpf_get_stackid()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ee2a098851bfbe8bcdd964c0121f4246f00ff41e · < 23f852daa4bab4d579110e034e4d513f7d490846| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s __bpf_get_stackid() can write past a stack map bucket when a perf trace contains more stack entries than the bucket can hold. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Engineers running Linux kernels with BPF stack map support should check their versions; affected versions are not specified.