CVE-2025-38636: rv: Use strings in da monitors tracepoints
In the Linux kernel, the following vulnerability has been resolved:
rv: Use strings in da monitors tracepoints
Using DA monitors tracepoints with KASAN enabled triggers the following warning:
BUG: KASAN: global-out-of-bounds in dotraceeventraweventeventdamonitor+0xd6/0x1a0 Read of size 32 at addr ffffffffaada8980 by task ... Call Trace: <TASK> [...] dotraceeventraweventeventdamonitor+0xd6/0x1a0 ? pfxdotraceeventraweventeventdamonitor+0x10/0x10 ? traceeventsncid+0x83/0x200 traceeventsncid+0x163/0x200 [...] The buggy address belongs to the variable: automatonsnep+0x4e0/0x5e0
This is caused by the tracepoints reading 32 bytes array instead of string from the automata definition. Such strings are literals and reading 32 bytes ends up in out of bound memory accesses (e.g. the next automaton's data in this case). The error is harmless as, while printing the string, we stop at the null terminator, but it should still be fixed.
Use the string facilities while defining the tracepoints to avoid reading out of bound memory.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch rv: Use strings in da monitors tracepoints
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38636?
CVE-2025-38636 has a medium severity rating as it involves a global-out-of-bounds access in the Linux kernel.
How do I fix CVE-2025-38636?
To fix CVE-2025-38636, users should update their Linux kernel to the latest stable version where the vulnerability has been patched.
Which software is affected by CVE-2025-38636?
CVE-2025-38636 affects the Linux kernel, particularly versions with KASAN enabled.
What does CVE-2025-38636 impact in the Linux kernel?
CVE-2025-38636 impacts the integrity of the tracing subsystem when using DA monitors tracepoints.
Is CVE-2025-38636 exploitable in production environments?
CVE-2025-38636 may be exploitable in production environments depending on the specific configurations and usage of tracing features.