CVE-2025-38493: tracing/osnoise: Fix crash in timerlat_dump_stack()
Noroxi assessment
Priority: Monitor (action score 22/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.18% (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 7bb9ea515cda027c9e717e27fefcf34f092e7c41, 823d798900481875ba6c68217af028c5ffd2976b, 85a3bce695b361d85fc528e6fbb33e4c8089c806; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 7bb9ea515cda027c9e717e27fefcf34f092e7c41, 823d798900481875ba6c68217af028c5ffd2976b, 85a3bce695b361d85fc528e6fbb33e4c8089c806; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 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: 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().
- Published
- Jul 28, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-674
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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 |
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
- 6.6affected
- e7186af7fb2609584a8bfb3da3c6ae09da5a5224 and later · before 823d798900481875ba6c68217af028c5ffd2976baffected · git
- e7186af7fb2609584a8bfb3da3c6ae09da5a5224 and later · before 7bb9ea515cda027c9e717e27fefcf34f092e7c41affected · git
- e7186af7fb2609584a8bfb3da3c6ae09da5a5224 and later · before fbf90f5aa7ac7cddc69148a71d58f12c8709ce2baffected · git
- e7186af7fb2609584a8bfb3da3c6ae09da5a5224 and later · before 85a3bce695b361d85fc528e6fbb33e4c8089c806affected · git
- before 6.6not affected · semver
- 6.6.100 and later · up to and including 6.6.*not affected · semver
- 6.12.40 and later · up to and including 6.12.*not affected · semver
- 6.15.8 and later · up to and including 6.15.*not affected · semver
- 6.16 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.6 and later · before 6.6.100
- linux linux kernel6.7 and later · before 6.12.40
- linux linux kernel6.13 and later · before 6.15.8
- linux linux kernel6.16
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.41-1 | 6.12.41-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-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-2025-38490Jul 28, 2025 · net: libwx: remove duplicate page_pool_put_full_page()31Monitor
- ← EarlierCVE-2025-38492Jul 28, 2025 · netfs: Fix race between cache write completion and ALL_QUEUED being set18Monitor
- Later →CVE-2025-38494Jul 28, 2025 · HID: core: do not bypass hid_hw_raw_request31Monitor
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 | 7bb9ea515cda027c9e717e27fefcf34f092e7c41 | Vendor (CNA) |
| Linux Linux | 823d798900481875ba6c68217af028c5ffd2976b | Vendor (CNA) |
| Linux Linux | 85a3bce695b361d85fc528e6fbb33e4c8089c806 | Vendor (CNA) |
| Linux Linux | fbf90f5aa7ac7cddc69148a71d58f12c8709ce2b | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.41-1 · Debian:13 | 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-43185282 days apartksmbd: fix signededness bug in smb_direct_prepare_negotiation()39Monitor
- CVE-2025-384593 days apartatm: clip: Fix infinite recursive call of clip_push().31Monitor
- CVE-2026-53202332 days apartaccel/ivpu: Fix signed integer truncation in IPC receive31Monitor
- CVE-2026-53267332 days apartnetfilter: nft_ct: bail out on template ct in get eval31Monitor
- CVE-2024-35886435 days apartipv6: Fix infinite recursion in fib6_dump_done().31Monitor
- CVE-2026-53395356 days apartnfsd: fix dead ACL conflict guard in nfsd4_create30Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-674 · Uncontrolled RecursionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.