CVE-2024-38588: ftrace: Fix possible use-after-free issue in ftrace_location()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1880a324af1c95940a7c954b6b937e86844a33bd, 31310e373f4c8c74e029d4326b283e757edabc0b, 66df065b3106964e667b37bf8f7e55ec69d0c1f6; CBL Mariner 2.0 ARM 5.15.167.1-2; CBL Mariner 2.0 x64 5.15.167.1-2.
Low priority for now. Upgrade to Linux Linux 1880a324af1c95940a7c954b6b937e86844a33bd, 31310e373f4c8c74e029d4326b283e757edabc0b, 66df065b3106964e667b37bf8f7e55ec69d0c1f6; CBL Mariner 2.0 ARM 5.15.167.1-2; CBL Mariner 2.0 x64 5.15.167.1-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Jun 19, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel3.7 and later · before 5.4.286
- linux linux kernel5.5 and later · before 5.10.227
- linux linux kernel5.11 and later · before 5.15.162
- linux linux kernel5.16 and later · before 6.1.93
- linux linux kernel6.2 and later · before 6.6.33
- linux linux kernel6.7 and later · before 6.8.12
- linux linux kernel6.9 and later · before 6.9.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.7affected
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before eea46baf145150910ba134f75a67106ba2222c1baffected · git
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before 1880a324af1c95940a7c954b6b937e86844a33bdaffected · git
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before 8ea8ef5e42173560ac510e92a1cc797ffeea8831affected · git
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before dbff5f0bfb2416b8b55c105ddbcd4f885e98fadaaffected · git
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before 7b4881da5b19f65709f5c18c1a4d8caa2e496461affected · git
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before 66df065b3106964e667b37bf8f7e55ec69d0c1f6affected · git
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before 31310e373f4c8c74e029d4326b283e757edabc0baffected · git
- ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b and later · before e60b613df8b6253def41215402f72986fee3fc8daffected · git
- before 3.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.234-1 | 5.10.234-1 |
| Debian:12 | linux | before 6.1.94-1 | 6.1.94-1 |
| Debian:13 | linux | before 6.8.12-1 | 6.8.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-38585Jun 19, 2024 · tools/nolibc/stdlib: fix memory error in realloc()28Monitor
- ← EarlierCVE-2024-38586Jun 19, 2024 · r8169: Fix possible ring buffer corruption on fragmented Tx packets.31Monitor
- Later →CVE-2024-38590Jun 19, 2024 · RDMA/hns: Modify the print level of CQE error22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1880a324af1c95940a7c954b6b937e86844a33bd | Vendor (CNA) |
| Linux Linux | 31310e373f4c8c74e029d4326b283e757edabc0b | Vendor (CNA) |
| Linux Linux | 66df065b3106964e667b37bf8f7e55ec69d0c1f6 | Vendor (CNA) |
| Linux Linux | 7b4881da5b19f65709f5c18c1a4d8caa2e496461 | Vendor (CNA) |
| Linux Linux | 8ea8ef5e42173560ac510e92a1cc797ffeea8831 | Vendor (CNA) |
| Linux Linux | dbff5f0bfb2416b8b55c105ddbcd4f885e98fada | Vendor (CNA) |
| Linux Linux | e60b613df8b6253def41215402f72986fee3fc8d | Vendor (CNA) |
| Linux Linux | eea46baf145150910ba134f75a67106ba2222c1b | Vendor (CNA) |
| CBL Mariner 2.0 ARM | 5.15.167.1-2 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 5.15.167.1-2 · kernel | Microsoft (MSRC) |
| debian:linux | 6.1.94-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/31310e373f4c8c74e029d4326b283e757edabc0b
- git.kernel.org/stable/c/66df065b3106964e667b37bf8f7e55ec69d0c1f6
- git.kernel.org/stable/c/7b4881da5b19f65709f5c18c1a4d8caa2e496461
- git.kernel.org/stable/c/8ea8ef5e42173560ac510e92a1cc797ffeea8831
- git.kernel.org/stable/c/dbff5f0bfb2416b8b55c105ddbcd4f885e98fada
- git.kernel.org/stable/c/e60b613df8b6253def41215402f72986fee3fc8d
- git.kernel.org/stable/c/eea46baf145150910ba134f75a67106ba2222c1b
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.