VulnerabilityPublished 22 Aug 2025Updated 21 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in dcae71222c8b9e5b5dd88a2d67347dedf10e68c6 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 16:39 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in dcae71222c8b9e5b5dd88a2d67347dedf10e68c6, 665ca03e93cee01baadc7b5eaee21b9d892e0dab, 7f904ff6e58d398c4336f3c19c42b338324451f7 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to dcae71222c8b9e5b5dd88a2d67347dedf10e68c6, 665ca03e93cee01baadc7b5eaee21b9d892e0dab, 7f904ff6e58d398c4336f3c19c42b338324451f7 or 0ebc70d973ce7a81826b5c4f55f743e07f5864d9.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 792575348ff70e05c6040d02fce38e949ef92c37, < dcae71222c8b9e5b5dd88a2d67347dedf10e68c6	Fixed in dcae71222c8b9e5b5dd88a2d67347dedf10e68c6
LinuxLinux	Affected ≥ 792575348ff70e05c6040d02fce38e949ef92c37, < 665ca03e93cee01baadc7b5eaee21b9d892e0dab	Fixed in 665ca03e93cee01baadc7b5eaee21b9d892e0dab
LinuxLinux	Affected ≥ 792575348ff70e05c6040d02fce38e949ef92c37, < 7f904ff6e58d398c4336f3c19c42b338324451f7	Fixed in 7f904ff6e58d398c4336f3c19c42b338324451f7
LinuxLinux	Affected ≥ 792575348ff70e05c6040d02fce38e949ef92c37, < 0ebc70d973ce7a81826b5c4f55f743e07f5864d9	Fixed in 0ebc70d973ce7a81826b5c4f55f743e07f5864d9
LinuxLinux	Affected =6.0	Fixed in–

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 __string facilities while defining the tracepoints to avoid reading out of bound memory.

References

Community reviews

Loading reviews…