CVE-2025-38636: rv: Use strings in da monitors tracepoints

Published Aug 22, 2025
·
Updated

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

7 affected components
Linux Linux kernel
Linux Linux kernel>=6.0<6.16.1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.96.2-1
Microsoft azl3 kernel 6.6.112.1-2
Microsoft azl3 kernel 6.6.104.2-4
Microsoft azl3 kernel 6.6.117.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch rv: Use strings in da monitors tracepoints

Event History

Aug 22, 2025
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 3, 2025
Data Sourced
via Microsoft·10:36 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·10:36 PM
SeverityAffected Software
Updated
via Microsoft·10:36 PM
Affected Software
Sep 4, 2025
Updated
via Microsoft·05:36 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

Which software is affected by CVE-2025-38636?

CVE-2025-38636 affects the Linux kernel, particularly versions with KASAN enabled.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203