CVE-2025-38636
BaseFortify
Publication date: 2025-08-22
Last updated on: 2025-11-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel when using DA monitors tracepoints with KASAN enabled. The tracepoints incorrectly read 32 bytes from an array instead of a string, causing out-of-bounds memory access. Although the error is harmless because printing stops at the null terminator, it involves reading memory beyond the intended bounds due to misuse of tracepoint definitions.
How can this vulnerability impact me? :
The vulnerability causes out-of-bounds memory reads, which can trigger warnings and potentially affect system stability or debugging processes. However, the error is considered harmless as the string printing stops at the null terminator, so it does not lead to direct memory corruption or exploitation.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by enabling KASAN (Kernel Address Sanitizer) and monitoring for the specific warning message: 'BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor'. You can check your kernel logs (e.g., using 'dmesg' or 'journalctl -k') for this warning. There are no specific commands provided to detect this vulnerability beyond monitoring for this KASAN warning.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to update the Linux kernel to a version where this issue is fixed by using __string facilities in the tracepoints instead of reading 32 bytes arrays, which prevents out-of-bounds memory access. Until then, avoid using DA monitors tracepoints with KASAN enabled to prevent triggering the warning.