🛡️ UBUNTU-CVE-2024-38588
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

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: 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().

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2024-06-19
Updated 2026-06-15
Modified 2026-06-04
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 6.8.0-40.40
linux-allwinner-5.19
linux-aws 6.8.0-1013.14
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1069.75~20.04.1
linux-aws-5.19
linux-aws-5.3
linux-aws-5.4 5.4.0-1142.152~18.04.1
linux-aws-5.8
linux-aws-6.2
linux-aws-6.5
linux-aws-6.8 6.8.0-1013.14~22.04.1
linux-aws-fips 5.15.0-1069.75+fips1
linux-aws-hwe
linux-azure 6.8.0-1012.14
linux-azure-4.15
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1072.81~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.4 5.4.0-1147.154~18.04.1
linux-azure-5.8
linux-azure-6.2
linux-azure-6.5
linux-azure-6.8 6.8.0-1012.14~22.04.1
linux-azure-edge
linux-azure-fde 5.15.0-1072.81.1
linux-azure-fde-5.19
linux-azure-fde-6.2
linux-azure-fips 5.15.0-1072.81+fips1
linux-bluefield
linux-fips 6.8.0-78.78+fips1
linux-gcp 6.8.0-1012.13
linux-gcp-4.15
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1068.76~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.4 5.4.0-1145.154~18.04.1
linux-gcp-5.8
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-6.8 6.8.0-1012.13~22.04.1
linux-gcp-fips 5.15.0-1068.76+fips1
linux-gke 6.8.0-1008.11
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 5.15.0-1052.59
linux-gkeop-5.15 5.15.0-1052.59~20.04.1
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-121.131~20.04.1
linux-hwe-5.19
linux-hwe-5.4 5.4.0-211.231~18.04.1
linux-hwe-5.8
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-6.8 6.8.0-40.40~22.04.3
linux-hwe-edge
linux-ibm 6.8.0-1010.10
linux-ibm-5.15 5.15.0-1062.65~20.04.1
linux-ibm-5.4 5.4.0-1090.95~18.04.1
linux-ibm-6.8 6.8.0-1010.10~22.04.1
linux-intel-5.13
linux-intel-iot-realtime 5.15.0-1063.65
linux-intel-iotg 5.15.0-1064.70
linux-intel-iotg-5.15 5.15.0-1064.70~20.04.1
linux-iot 5.4.0-1048.51
linux-kvm 5.15.0-1066.71
linux-lowlatency 6.8.0-40.40.1
linux-lowlatency-hwe-5.15 5.15.0-121.131~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lowlatency-hwe-6.8 6.8.0-40.40.1~22.04.1
linux-lts-xenial
linux-nvidia 6.8.0-1011.11
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-6.8 6.8.0-1011.11~22.04.1
linux-nvidia-lowlatency 6.8.0-1011.11.1
linux-nvidia-tegra 5.15.0-1028.28
linux-nvidia-tegra-5.15 5.15.0-1030.30~20.04.1
linux-nvidia-tegra-igx 5.15.0-1016.16
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.5
linux-oem-6.8 6.8.0-1010.10
linux-oracle 6.8.0-1010.10
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1067.73~20.04.1
linux-oracle-5.3
linux-oracle-5.4 5.4.0-1140.149~18.04.1
linux-oracle-5.8
linux-oracle-6.5
linux-oracle-6.8 6.8.0-1010.10~22.04.1
linux-raspi 6.8.0-1009.10
linux-raspi-5.4 5.4.0-1129.142~18.04.1
linux-raspi-realtime 6.8.0-2008.8
linux-raspi2
linux-realtime 6.8.1-1006.6
linux-realtime-6.8 6.8.1-1006.6~22.04.1
linux-riscv 6.8.0-40.40.1
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1065.69~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.5
linux-riscv-6.8 6.8.0-40.40.1~22.04.1
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx-zynqmp 5.15.0-1035.39

References

Similar Threats

Vulnerability Monitoring

Stay informed about vulnerabilities in your stack

BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.