cbcvebase.
CVE-2024-38588
published 2024-06-19

CVE-2024-38588: In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix possible use-after-free issue in ftrace_location() KASAN reports a bug: BUG…

PriorityP338high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.24%
14.9th percentile
In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix possible use-after-free issue in ftrace_location() KASAN reports a bug: BUG: KASAN: use-after-free in ftrace_location+0x90/0x120 Read of size 8 at addr ffff888141d40010 by task insmod/424 CPU: 8 PID: 424 Comm: insmod Tainted: G W 6.9.0-rc2+ [...] Call Trace: dump_stack_lvl+0x68/0xa0 print_report+0xcf/0x610 kasan_report+0xb5/0xe0 ftrace_location+0x90/0x120 register_kprobe+0x14b/0xa40 kprobe_init+0x2d/0xff0 [kprobe_example] do_one_initcall+0x8f/0x2d0 do_init_module+0x13a/0x3c0 load_module+0x3082/0x33d0 init_module_from_file+0xd2/0x130 __x64_sys_finit_module+0x306/0x440 do_syscall_64+0x68/0x140 entry_SYSCALL_64_after_hwframe+0x71/0x79 The root cause is that, in lookup_rec(), ftrace record of some address is being searched in ftrace pages of some module, but those ftrace pages at the same time is being freed in ftrace_release_mod() as the corresponding module is being deleted: CPU1 | CPU2 register_kprobes() { | delete_module() { check_kprobe_address_safe() { | arch_check_ftrace_location() { | ftrace_location() { | lookup_rec() // USE! | ftrace_release_mod() // Free! To fix this issue: 1. Hold rcu lock as accessing ftrace pages in ftrace_location_range(); 2. Use ftrace_location_range() instead of lookup_rec() in ftrace_location(); 3. Call synchronize_rcu() before freeing any ftrace pages both in ftrace_process_locs()/ftrace_release_mod()/ftrace_free_mem().

Affected

29 ranges· showing 25
VendorProductVersion rangeFixed in
debiandebian_linux
debianlinux< linux 6.1.94-1 (bookworm)linux 6.1.94-1 (bookworm)
linuxlinux
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < eea46baf145150910ba134f75a67106ba2222c1beea46baf145150910ba134f75a67106ba2222c1b
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < 1880a324af1c95940a7c954b6b937e86844a33bd1880a324af1c95940a7c954b6b937e86844a33bd
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < 8ea8ef5e42173560ac510e92a1cc797ffeea88318ea8ef5e42173560ac510e92a1cc797ffeea8831
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < dbff5f0bfb2416b8b55c105ddbcd4f885e98fadadbff5f0bfb2416b8b55c105ddbcd4f885e98fada
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < 7b4881da5b19f65709f5c18c1a4d8caa2e4964617b4881da5b19f65709f5c18c1a4d8caa2e496461
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < 66df065b3106964e667b37bf8f7e55ec69d0c1f666df065b3106964e667b37bf8f7e55ec69d0c1f6
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < 31310e373f4c8c74e029d4326b283e757edabc0b31310e373f4c8c74e029d4326b283e757edabc0b
linuxlinux>= ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b < e60b613df8b6253def41215402f72986fee3fc8de60b613df8b6253def41215402f72986fee3fc8d
linuxlinux_kernel>= 0 < 5.10.234-15.10.234-1
linuxlinux_kernel>= 0 < 6.1.94-16.1.94-1
linuxlinux_kernel>= 0 < 6.8.12-16.8.12-1
linuxlinux_kernel>= 0 < 6.8.12-16.8.12-1
linuxlinux_kernel>= 0 < 5.4.0-211.2315.4.0-211.231
linuxlinux_kernel>= 0 < 5.15.0-121.1315.15.0-121.131
linuxlinux_kernel>= 0 < 6.8.0-40.406.8.0-40.40
linuxlinux_kernel>= 3.7 < 5.4.2865.4.286
linuxlinux_kernel>= 5.11 < 5.15.1625.15.162
linuxlinux_kernel>= 5.16 < 6.1.936.1.93
linuxlinux_kernel>= 5.5 < 5.10.2275.10.227
linuxlinux_kernel>= 6.2 < 6.6.336.6.33
linuxlinux_kernel>= 6.7 < 6.8.126.8.12
linuxlinux_kernel>= 6.9 < 6.9.36.9.3

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_msrc7.8HIGH
vendor_redhat7.8HIGH
vendor_ubuntu6.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.