Menu

Star on GitHub · 3.2k

CVE-2025-38636

7.1 · HIGH

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: B…

Published Aug 22, 2025CWE-125EPSS 0.15%

Overview

CVE-2025-38636 is a high-severity vulnerability. It was published on August 22, 2025 and has a CVSS 3.1 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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 do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0

Read of size 32 at addr ffffffffaada8980 by task ...

Call Trace:

<TASK>

[...]

do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0

? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10

? trace_event_sncid+0x83/0x200

trace_event_sncid+0x163/0x200

[...]

The buggy address belongs to the variable:

automaton_snep+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 __

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-38636?

CVE-2025-38636 is a high-severity vulnerability. It was published on August 22, 2025 and has a CVSS 3.1 base score of 7.1 (HIGH).

How severe is CVE-2025-38636?

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-38636?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38636?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38636 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all