CVE-2025-61661MediumMicrosoft CVSS 4.8CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H/E:U

Microsoft security update for CVE-2025-61661

Published
May 31, 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-61661. This page also shows what EchelonGraph holds for CVE-2025-61661, 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 grub2 2.06-25 on Azure Linux 3.0
  • azl3 grub2 2.06-26 on Azure Linux 3.0
  • cbl2 grub2 2.06-15 on CBL Mariner 2.0
  • cbl2 grub2 2.06-16 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 Update2.06-16
—Security Update2.06-26

🧭 EchelonGraph on CVE-2025-61661

EchelonGraph score
4.8 MEDIUM
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 vulnerability has been identified in the GRUB (Grand Unified Bootloader) component. This flaw occurs because the bootloader mishandles string conversion when reading information from a USB device, allowing an attacker to exploit inconsistent length values. A local attacker can connect a maliciously configured USB device during the boot sequence to trigger this issue. A successful exploitation may lead GRUB to crash, leading to a Denial of Service. Data corruption may be also possible, although given the complexity of the exploit the impact is most likely limited.

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