CVE-2025-38493
tracing/osnoise: Fix crash in timerlat_dump_stack()
Reported by linux · Published July 28, 2025
In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Fix crash in timerlat_dump_stack() We have observed kernel panics when using timerlat with stack saving, with the following dmesg output: memcpy: detected buffer overflow: 88 byte write of buffer size 0 WARNING: CPU: 2 PID: 8153 at lib/string_helpers.c:1032 __fortify_report+0x55/0xa0 CPU: 2 UID: 0 PID: 8153 Comm: timerlatu/2 Kdump: loaded Not tainted 6.15.3-200.fc42.x86_64 #1 PREEMPT(lazy) Call Trace: <TASK> ? trace_buffer_lock_reserve+0x2a/0x60 __fortify_panic+0xd/0xf __timerlat_dump_stack.cold+0xd/0xd timerlat_dump_stack.part.0+0x47/0x80 timerlat_fd_read+0x36d/0x390 vfs_read+0xe2/0x390 ? syscall_exit_to_user_mode+0x1d5/0x210 ksys_read+0x73/0xe0 do_syscall_64+0x7b/0x160 ? exc_page_fault+0x7e/0x1a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e __timerlat_dump_stack() constructs the ftrace stack entry like this: struct stack_entry *entry; ... memcpy(&entry->caller, fstack->calls, size); entry->size = fstack->nr_entries; Since commit e7186af7fb26 ("tracing: Add back FORTIFY_SOURCE logic to kernel_stack event structure"), struct stack_entry marks its caller field with __counted_by(size). At the time of the memcpy, entry->size contains garbage from the ringbuffer, which under some circumstances is zero, triggering a kernel panic by buffer overflow. Populate the size field before the memcpy so that the out-of-bounds check knows the correct size. This is analogous to __ftrace_trace_stack().
EPSS 0.18% · 8.0th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12 | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-tools | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-modules-extra | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-libbpf-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel-livepatch-6.12.40-63.114 | Amazon Linux | 1:1.0-0.amzn2023 |
| bpftool6.12 | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel6.12-libbpf-static | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| linux_kernel | linux | 6.15.8, 6.12.40, 6.6.100 |
| Linux | Linux | fbf90f5aa7ac7cddc69148a71d58f12c8709ce2b, 85a3bce695b361d85fc528e6fbb33e4c8089c806, 823d798900481875ba6c68217af028c5ffd2976b, 7bb9ea515cda027c9e717e27fefcf34f092e7c41 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | e7186af7fb2609584a8bfb3da3c6ae09da5a5224, e7186af7fb2609584a8bfb3da3c6ae09da5a5224, e7186af7fb2609584a8bfb3da3c6ae09da5a5224 |
| Linux | Linux | 6.6, 0, 6.6.100 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel-livepatch-6.12.40-63.114 | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| Linux | Linux | *, *, * |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-libbpf | 0 |
| linux | linux_kernel | 6.6, 6.6, 6.6 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | perf6.12 | 0 |
Timeline
- Jul 28, 2025 EPSS Score (30 in total, the first dated here)
- Jul 28, 2025 CVE Published
- Oct 12, 2025 PoC Published (10 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (157 in total, the first dated here)
- Mar 29, 2026 Security Advisory (203 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
- Oct 7, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38493
vulnetix vdb fixes CVE-2025-38493
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38493/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart