# CVE-2025-24857: Missing authorization in n/a

> Attackers can execute arbitrary code due to improper access control in U-Boot bootloader memory on Qualcomm chips.

- **Severity:** High 7.6 (`CVSS:3.1/AC:L/AV:P/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Dec 2025
- **Updated:** 23 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-24857, GHSA-v72w-97m6-622r, UBUNTU-CVE-2025-24857

## What is CVE-2025-24857?

CVE-2025-24857 is a high-severity missing authorization vulnerability in n/a, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control for volatile memory containing boot code in Universal Boot Loader (U-Boot) before 2017.11 and Qualcomm chips IPQ4019, IPQ5018, IPQ5322, IPQ6018, IPQ8064, IPQ8074, and IPQ9574 could allow an attacker to execute arbitrary code.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Denx U-Boot.

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

Upgrade to a fixed version.

## Is CVE-2025-24857 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-34835](https://insights.sbomify.com/CVE-2022-34835/): Integer overflow in n/a (critical 9.8)
- [CVE-2022-30767](https://insights.sbomify.com/CVE-2022-30767/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-8432](https://insights.sbomify.com/CVE-2020-8432/): Use after free in n/a (critical 9.8)
- [CVE-2019-14192](https://insights.sbomify.com/CVE-2019-14192/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-14193](https://insights.sbomify.com/CVE-2019-14193/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24857 is a high-severity missing authorization vulnerability in n/a, published on 10 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24857 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-24857/ (Markdown: https://insights.sbomify.com/CVE-2025-24857/index.md)
```

## Sources

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

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