bpf: Fix stackmap overflow check in __bpf_get_stackid()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.11, 5.16, 5.17, 5.18, 6.6.160, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ee2a098851bfbe8bcdd964c0121f4246f00ff41e · fixed in d6028caa0ee39dccd005468adfa3223b92bd3ad3; From ee2a098851bfbe8bcdd964c0121f4246f00ff41e · fixed in d1f424a77b6bd27b361737ed73df49a0158f1590; From ee2a098851bfbe8bcdd964c0121f4246f00ff41e · fixed in 2a008f6de163279deffd488c1deab081bce5667c; From ee2a098851bfbe8bcdd964c0121f4246f00ff41e · fixed in 4669a8db976c8cbd5427fe9945f12c5fa5168ff3; From ee2a098851bfbe8bcdd964c0121f4246f00ff41e · fixed in 23f852daa4bab4d579110e034e4d513f7d490846; From 5.10.110 · fixed in 5.11; From 5.15.33 · fixed in 5.16; From 5.16.19 · fixed in 5.17; From 5.17.2 · fixed in 5.18
- Linux Linux
5.18
- KernelLinux
From 5.18.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.63; From 6.13.0 · fixed in 6.17.13; From 6.18.0 · fixed in 6.18.2