CVE-2024-38588
LTE1435 Linux KASAN- Linked List Corruption
Description
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: <TASK> 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().
INFO
Published Date :
June 19, 2024, 2:15 p.m.
Last Modified :
Sept. 19, 2024, 1:19 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
5.9
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-38588.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-38588 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-38588 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Sep. 19, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://git.kernel.org/stable/c/31310e373f4c8c74e029d4326b283e757edabc0b No Types Assigned https://git.kernel.org/stable/c/31310e373f4c8c74e029d4326b283e757edabc0b Patch Changed Reference Type https://git.kernel.org/stable/c/66df065b3106964e667b37bf8f7e55ec69d0c1f6 No Types Assigned https://git.kernel.org/stable/c/66df065b3106964e667b37bf8f7e55ec69d0c1f6 Patch Changed Reference Type https://git.kernel.org/stable/c/7b4881da5b19f65709f5c18c1a4d8caa2e496461 No Types Assigned https://git.kernel.org/stable/c/7b4881da5b19f65709f5c18c1a4d8caa2e496461 Patch Changed Reference Type https://git.kernel.org/stable/c/8ea8ef5e42173560ac510e92a1cc797ffeea8831 No Types Assigned https://git.kernel.org/stable/c/8ea8ef5e42173560ac510e92a1cc797ffeea8831 Patch Changed Reference Type https://git.kernel.org/stable/c/dbff5f0bfb2416b8b55c105ddbcd4f885e98fada No Types Assigned https://git.kernel.org/stable/c/dbff5f0bfb2416b8b55c105ddbcd4f885e98fada Patch Changed Reference Type https://git.kernel.org/stable/c/e60b613df8b6253def41215402f72986fee3fc8d No Types Assigned https://git.kernel.org/stable/c/e60b613df8b6253def41215402f72986fee3fc8d Patch Added CWE NIST CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 3.7 up to (excluding) 6.1.93 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.8.12 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.9 up to (excluding) 6.9.3 -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 05, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/8ea8ef5e42173560ac510e92a1cc797ffeea8831 [No types assigned] -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 19, 2024
Action Type Old Value New Value Added Description 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: <TASK> 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(). Added Reference kernel.org https://git.kernel.org/stable/c/dbff5f0bfb2416b8b55c105ddbcd4f885e98fada [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/7b4881da5b19f65709f5c18c1a4d8caa2e496461 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/66df065b3106964e667b37bf8f7e55ec69d0c1f6 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/31310e373f4c8c74e029d4326b283e757edabc0b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e60b613df8b6253def41215402f72986fee3fc8d [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-38588 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-38588
weaknesses.