CVE-2025-38636 json
rv: Use strings in da monitors tracepoints
published 2025-08-22 14 mo ago modified 2026-11-05 3 d ago also EUVD-2025-25565
- cvss
- 7.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.16.1, 6.17
- linux Debian 13 6.12.115-2
- linux Debian 14 6.16.3-1
debian advisories DEBIAN-CVE-2025-38636
- linux-nvidia-tegra Ubuntu 24.04 LTS 6.8.0-1035.38
ubuntu advisories UBUNTU-CVE-2025-38636
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/cb8de6f5ed5c43f7387615bbe601d2a4a31b7b35 commit
- git.kernel.org/stable/c/dcae71222c8b9e5b5dd88a2d67347dedf10e68c6 commit
- git.kernel.org/stable/c/665ca03e93cee01baadc7b5eaee21b9d892e0dab commit
- git.kernel.org/stable/c/0ebc70d973ce7a81826b5c4f55f743e07f5864d9 commit
- git.kernel.org/stable/c/7f904ff6e58d398c4336f3c19c42b338324451f7 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-38636 updated cvss 4.4
kernel: rv: Use strings in da monitors tracepoints
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
- git.kernel.org /stable/c/cb8de6f5ed5c43f7387615bbe601d2a4a31b7b35
- git.kernel.org /stable/c/dcae71222c8b9e5b5dd88a2d67347dedf10e68c6
- git.kernel.org /stable/c/665ca03e93cee01baadc7b5eaee21b9d892e0dab
-
git.kernel.org
/stable/c/0ebc70d973ce7a81826b5c4f55f743e07f5864d9
patch
-
git.kernel.org
/stable/c/7f904ff6e58d398c4336f3c19c42b338324451f7
patch
Sources
- CVE List CVE-2025-38636
- NVD CVE-2025-38636
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.