CVE-2025-26601HighMicrosoft CVSS 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Microsoft security update for CVE-2025-26601

Published
June 3, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 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-26601. This page also shows what EchelonGraph holds for CVE-2025-26601, 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 products4

  • azl3 xorg-x11-server-Xwayland 24.1.1-3 on Azure Linux 3.0
  • azl3 xorg-x11-server-Xwayland 24.1.6-1 on Azure Linux 3.0
  • cbl2 xorg-x11-server 1.20.10-15 on CBL Mariner 2.0
  • cbl2 xorg-x11-server 1.20.10-15 on CBL-Mariner 2.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 Update24.1.6-1
—Security Update1.20.10-15

🧭 EchelonGraph on CVE-2025-26601

EchelonGraph score
7.8 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

A use-after-free flaw was found in X.Org and Xwayland. When changing an alarm, the values of the change mask are evaluated one after the other, changing the trigger values as requested, and eventually, SyncInitTrigger() is called. If one of the changes triggers an error, the function will return early, not adding the new sync object, possibly causing a use-after-free when the alarm eventually triggers.

Published by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2025-26601, 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)