summaryrefslogtreecommitdiff
path: root/include/linux/tracepoint.h
diff options
context:
space:
mode:
authorChen Zhongjin <chenzhongjin@huawei.com>2023-03-09 11:02:30 +0300
committerSteven Rostedt (Google) <rostedt@goodmis.org>2023-03-10 06:17:06 +0300
commitee92fa443358f4fc0017c1d0d325c27b37802504 (patch)
tree9d7a0ed5f76b393ae3c72086a916904b251a9d80 /include/linux/tracepoint.h
parent9f116f76fa8c04c81aef33ad870dbf9a158e5b70 (diff)
downloadlinux-ee92fa443358f4fc0017c1d0d325c27b37802504.tar.xz
ftrace: Fix invalid address access in lookup_rec() when index is 0
KASAN reported follow problem: BUG: KASAN: use-after-free in lookup_rec Read of size 8 at addr ffff000199270ff0 by task modprobe CPU: 2 Comm: modprobe Call trace: kasan_report __asan_load8 lookup_rec ftrace_location arch_check_ftrace_location check_kprobe_address_safe register_kprobe When checking pg->records[pg->index - 1].ip in lookup_rec(), it can get a pg which is newly added to ftrace_pages_start in ftrace_process_locs(). Before the first pg->index++, index is 0 and accessing pg->records[-1].ip will cause this problem. Don't check the ip when pg->index is 0. Link: https://lore.kernel.org/linux-trace-kernel/20230309080230.36064-1-chenzhongjin@huawei.com Cc: stable@vger.kernel.org Fixes: 9644302e3315 ("ftrace: Speed up search by skipping pages by address") Suggested-by: Steven Rostedt (Google) <rostedt@goodmis.org> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'include/linux/tracepoint.h')
0 files changed, 0 insertions, 0 deletions