ftrace: Fix invalid address access in lookup_rec() when index is 0
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9644302e3315e7e36495d230d5ac7125a316d33e · < 4f84f31f63416b0f02fc146ffdc4ab32723eb7e8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
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.
From the CVE record · Linux
The Linux kernel’s ftrace lookup_rec() can access an invalid address when a newly added page has an index of zero. This can cause a use-after-free read during kprobe registration; the report shows it in a local modprobe task. The input does not establish attacker privileges or user-interaction requirements.
Engineers running Linux kernels with ftrace should check their kernel versions; affected versions are not specified.