LiveActive security incident?Get immediate response
CVE Record

CVE-2025-70293: An issue was discovered in Denx U-Boot before 2026.04.

An issue was discovered in Denx U-Boot before 2026.04. An integer overflow vulnerability exists in function ext4fs_get_bgdtable, the size calculation can lead to under allocation and this underallocated buffer will be used in memcpy() which could lead to arbitrary code execution, a denial of service, or other unspecified impacts.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A size calculation in Denx U-Boot before 2026.04 can overflow, creating a buffer smaller than expected. A subsequent memory copy may corrupt memory, potentially causing code execution, service disruption, or other impacts. The available record does not identify specific devices, vendors, attack prerequisites, or severity.

Executive priority

Begin targeted inventory and vendor confirmation promptly, especially for exposed, safety-critical, or difficult-to-recover devices. Potential code execution makes the issue consequential, but priority cannot be rated reliably until product exposure, attack prerequisites, and remediation status are established.

Technical view

The vulnerability is in ext4fs_get_bgdtable. Integer overflow during size calculation can cause under-allocation, followed by memcpy() into the undersized buffer. The stated consequences include arbitrary code execution and denial of service, but the source bundle provides no CVSS score, CWE, affected configuration details, or confirmed exploitation path.

Likely exposure

Potential exposure includes systems incorporating Denx U-Boot versions before 2026.04 where the vulnerable ext4 filesystem code is present and reachable. Actual exposure cannot be determined from the supplied data because downstream products, configurations, access requirements, and affected version ranges beyond the stated cutoff are not identified.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation. Although arbitrary code execution is described as possible, the available evidence does not establish exploit maturity, required access, attacker-controlled input conditions, or real-world prevalence.

Researcher notes

The described primitive is integer-overflow-driven heap or buffer under-allocation followed by memcpy(). Important missing evidence includes the exact arithmetic, architecture dependence, controllable filesystem fields, memory-corruption boundaries, affected commits, and patch details. Avoid treating possible code execution as demonstrated exploitation without further source evidence.

Mitigation direction

  • Inventory devices and firmware containing Denx U-Boot, including versions supplied by downstream vendors.
  • Prioritize systems running U-Boot releases before 2026.04 for vendor review.
  • Check Denx and device-vendor guidance for confirmed patches, backports, and supported upgrade paths.
  • Assess upgrading to 2026.04 or later only after confirming vendor applicability and compatibility.
  • Restrict untrusted access to affected boot and storage workflows where operationally feasible.

Validation and detection

  • Confirm the embedded U-Boot version from firmware inventories, build records, or vendor documentation.
  • Determine whether ext4fs_get_bgdtable and ext4 filesystem support are included in each deployed build.
  • Verify whether potentially untrusted ext4 media or images can reach the vulnerable code path.
  • Confirm remediation using vendor advisories, patch identifiers, or updated firmware release notes.
  • Monitor CVE and vendor records for CVSS, affected-product, and exploitation updates.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-70293 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.