# CVE-2025-70290: Integer overflow in n/a

> An integer overflow in U-Boot's ZFS support allows attackers to trigger out-of-bounds memory access, potentially leading to arbitrary code execution or crashes during boot.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** DEBIAN-CVE-2025-70290, GHSA-j2xx-grh4-4p3q, UBUNTU-CVE-2025-70290

## What is CVE-2025-70290?

CVE-2025-70290 is a critical vulnerability in n/a, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Denx U-Boot before 2026.04. An integer overflow vulnerability in the ZFS filesystem support can be triggered by malformed on-disk metadata. The issue may result in incorrect memory allocation followed by out-of-bounds memory access, potentially leading to a crash or arbitrary code execution during the boot process.

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-70290?


## How do I fix CVE-2025-70290?

Upgrade to a fixed version.

## Is CVE-2025-70290 being exploited?

There is no known exploitation of CVE-2025-70290 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70290 and fix it if it is affected.

What it is: CVE-2025-70290 is a critical vulnerability in n/a, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70290 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70290/ (Markdown: https://insights.sbomify.com/CVE-2025-70290/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70290
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70290
- OSV: https://osv.dev/vulnerability/CVE-2025-70290

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70290/
Summaries are generated and may contain mistakes; the official description above is the record.