Security readout for executives and security teams
Plain-English summary
This issue affects barebox systems that parse untrusted ext4 filesystems during boot. A malicious USB, SD card, or network-boot image can crash or disrupt boot-time parsing. The main business impact is device availability, especially for embedded or field devices that rely on removable or network boot media.
Executive priority
Treat this as a targeted availability risk for embedded devices and provisioning workflows, not a broad enterprise emergency. Prioritize internet-edge-adjacent, physically accessible, field-deployed, or network-booted devices first, then roll the fixed barebox release into normal firmware maintenance.
Technical view
In barebox before 2026.04.0, ext4 extent parsing in fs/ext4/ext4_common.c fails to validate eh_entries against buffer capacity. A crafted extent header can cause heap out-of-bounds reads while parsing filesystem metadata, potentially steering reads to arbitrary disk offsets. The CVSS vector indicates local attack, low complexity, no privileges, no user interaction, and high vulnerable-system availability impact.
Likely exposure
Exposure is likely limited to devices using barebox with ext4 boot media or filesystem parsing reachable from USB, SD card, or network boot. Systems not using barebox, not parsing ext4, or not accepting attacker-controlled boot media are less likely exposed. Version evidence should be checked against the installed barebox release.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires supplying a malicious ext4 filesystem image through a boot or storage path barebox parses. This is primarily a physical, local, or provisioning-chain risk rather than an internet-reachable server flaw.
Researcher notes
The affected-version metadata in the bundle is sparse, but the description states barebox before 2026.04.0. Key validation points are ext4 parsing reachability, boot source trust boundaries, and whether downstream firmware vendors have incorporated the patched release. Do not assume exploit activity without additional evidence.
Mitigation direction
- Upgrade barebox to version 2026.04.0 or later where feasible.
- Check barebox vendor release notes and advisory guidance before deploying fixes.
- Restrict USB, SD card, and network boot sources to trusted media.
- Disable unnecessary removable-media or network-boot paths where operationally possible.
- Add provisioning controls to prevent untrusted filesystem images from reaching devices.
Validation and detection
- Inventory products and firmware images that include barebox.
- Confirm installed barebox versions against the 2026.04.0 fixed release.
- Identify whether devices parse ext4 filesystems during boot.
- Review whether USB, SD, or network boot is exposed to untrusted parties.
- Check vendor firmware updates that incorporate the patched barebox release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-125: 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.
Open ATT&CK lookupCVE-2026-34961 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.53.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
6.2MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/barebox/bareboxCVE reference, VulnCheck · product
- https://github.com/barebox/barebox/releases/tag/v2026.04.0CVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/barebox-ext4-extent-parsing-out-of-bounds-readCVE reference, VulnCheck · third-party-advisory
- Blog PostCVE reference, VulnCheck · technical-description
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.