ftrace: Fix possible use-after-free issue in ftrace_location()
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().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.227, 5.15.162, 5.4.286, 6.1.93, 6.6.33, 6.8.12, 6.9.3
- CVEs
- CVE-2024-38588
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 04:42 UTC · Revision 1
Source evidence
ftrace: Fix possible use-after-free issue in ftrace_location()
core-osv · Original sourcePublished 19 Jun 2024, 13:37 UTC
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().
osv:CVE-2024-38588
Kernel
Fixed versions: 5.4.286, 5.10.227, 5.15.162, 6.1.93, 6.6.33, 6.8.12, 6.9.3
Complete source record
{
"id": "f9adf48573bfe4c6049db4bc414483edff189e676acaef3214dd2af5f365aefb",
"url": "https://osv.dev/vulnerability/CVE-2024-38588",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ftrace: Fix possible use-after-free issue in ftrace_location()",
"summary": "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().",
"evidence": "osv:CVE-2024-38588",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.286",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.227",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.162",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.93",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.33",
"evidence": "/affected/1/ranges"
},
{
"value": "6.8.12",
"evidence": "/affected/1/ranges"
},
{
"value": "6.9.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-38588",
"aliases": [
"CVE-2024-38588"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b"
},
{
"fixed": "eea46baf145150910ba134f75a67106ba2222c1b"
},
{
"fixed": "1880a324af1c95940a7c954b6b937e86844a33bd"
},
{
"fixed": "8ea8ef5e42173560ac510e92a1cc797ffeea8831"
},
{
"fixed": "dbff5f0bfb2416b8b55c105ddbcd4f885e98fada"
},
{
"fixed": "7b4881da5b19f65709f5c18c1a4d8caa2e496461"
},
{
"fixed": "66df065b3106964e667b37bf8f7e55ec69d0c1f6"
},
{
"fixed": "31310e373f4c8c74e029d4326b283e757edabc0b"
},
{
"fixed": "e60b613df8b6253def41215402f72986fee3fc8d"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-38588.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.7.0"
},
{
"fixed": "5.4.286"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.227"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.162"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.93"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.33"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.8.12"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.9.0"
},
{
"fixed": "6.9.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-38588.json"
}
}
],
"modified": "2026-10-28T02:30:50.175811086Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1880a324af1c95940a7c954b6b937e86844a33bd",
"https://git.kernel.org/stable/c/31310e373f4c8c74e029d4326b283e757edabc0b",
"https://git.kernel.org/stable/c/66df065b3106964e667b37bf8f7e55ec69d0c1f6",
"https://git.kernel.org/stable/c/7b4881da5b19f65709f5c18c1a4d8caa2e496461",
"https://git.kernel.org/stable/c/8ea8ef5e42173560ac510e92a1cc797ffeea8831",
"https://git.kernel.org/stable/c/dbff5f0bfb2416b8b55c105ddbcd4f885e98fada",
"https://git.kernel.org/stable/c/e60b613df8b6253def41215402f72986fee3fc8d",
"https://git.kernel.org/stable/c/eea46baf145150910ba134f75a67106ba2222c1b",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38588.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-38588",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38588.json"
}
},
"related_cves": [
{
"value": "CVE-2024-38588",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 518220,
"published_at": "2024-06-19T13:37:43.262+00:00"
}