CVE-2025-38636MediumMicrosoft CVSS 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Microsoft security update for CVE-2025-38636 — azl3 kernel

Published
September 3, 2025
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2025-38636 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-38636. This page also shows what EchelonGraph holds for CVE-2025-38636, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products23

  • azl3 kernel 6.6.104.2-4 on Azure Linux 3.0
  • azl3 kernel 6.6.112.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.117.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.119.3-1 on Azure Linux 3.0
  • azl3 kernel 6.6.119.3-3 on Azure Linux 3.0
  • azl3 kernel 6.6.121.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.126.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.130.1-3 on Azure Linux 3.0
  • azl3 kernel 6.6.134.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.137.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.138.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.139.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.141.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.143.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.144.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.145.2-1 on Azure Linux 3.0
  • azl3 kernel 6.6.150.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.152.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.157.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.161.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.96.2-1 on Azure Linux 3.0
  • azl3 kernel 6.6.96.2-2 on Azure Linux 3.0

✅ Updates Microsoft lists: 2 updates

2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—
—Security Update—

🧭 EchelonGraph on CVE-2025-38636

EchelonGraph score
7.1 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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.

Published by kernel.org, the CVE Numbering Authority that assigned CVE-2025-38636, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)