CVE-2025-61661: Grub2: grub2: out-of-bounds write via malicious usb device
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.
Security readout for executives and security teams
Plain-English summary
A malicious USB device connected during startup can trigger a memory-writing error in GRUB2. A successful attack could crash the bootloader, preventing normal startup, and may corrupt data. Exploitation requires physical access and is described as complex, limiting broad attack likelihood.
Executive priority
Treat this as a targeted physical-access resilience issue, not an internet-scale emergency. Prioritize systems in public, shared, remote, or weakly controlled locations. For well-controlled data centers, handle through normal patch governance while maintaining strict console and USB access controls.
Technical view
GRUB2 mishandles string conversion while processing USB device information with inconsistent length values, causing an out-of-bounds write classified as CWE-131. The CVSS 3.1 score is 4.8, reflecting physical access, high complexity, high availability impact, and possible low integrity impact.
Likely exposure
The bundle identifies GRUB2 packages in Red Hat Enterprise Linux 7 through 10 and Red Hat OpenShift Container Platform 4 as affected. Systems where untrusted people can attach USB devices during boot or reboot have the clearest exposure. Exact affected and fixed package versions are not provided.
Exploitation context
The attacker must locally connect a specially configured USB device during the boot sequence. No privileges or user interaction are required, but physical access and high attack complexity reduce practical reach. The CVE is not listed as known exploited, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The supplied evidence supports an out-of-bounds write and likely denial of service, with possible data corruption. It does not establish code execution, reliable exploitation, public exploit availability, or active attacks. Fixed versions and vendor-specific remediation details are absent, so package-level conclusions require current Red Hat guidance.
Mitigation direction
Check Red Hat guidance for corrected GRUB2 or platform packages and apply supported updates when available.
Restrict physical access to systems, consoles, and exposed USB ports.
Prevent unauthorized USB devices from remaining connected during startup or maintenance reboots.
Prioritize externally accessible, shared-site, kiosk, edge, and unattended systems for review.
Validation and detection
Inventory RHEL 7 through 10 and OpenShift 4 systems using the affected GRUB2 packages.
Compare installed bootloader and platform package versions with current Red Hat guidance.
Identify systems where untrusted users can access USB ports during boot or reboot.
Confirm relevant updates are deployed after Red Hat publishes fixed package information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-131: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-131 · source CWE mapping
Incorrect Calculation of Buffer Size
Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.