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

> An integer overflow in the Dolby DD+ decoder allows out-of-bounds writes, potentially leading to code execution or crashes on Android devices.

- **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:** 20 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** A-438955204, ASB-A-438955204, GHSA-rj4r-gj6w-jfgc, PUB-A-438955204

## What is CVE-2025-54957?

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

### Official description

An issue was discovered in Dolby UDC 4.5 through 4.13. A crash of the DD+ decoder process can occur when a malformed DD+ bitstream is processed. When Evolution data is processed by evo_priv.c from the DD+ bitstream, the decoder writes that data into a buffer. The length calculation for a write can overflow due to an integer wraparound. This can lead to the allocated buffer being too small, and the out-of-bounds check of the subsequent write to be ineffective, leading to an out-of-bounds write.

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

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


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

Apply the vendor's patch.

## Is CVE-2025-54957 being exploited?

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

Public exploit code:

- CVE-2025-54957 (github_poc): https://github.com/AlphabugX/CVE-2025-54957

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54957 is a critical vulnerability in n/a, published on 20 Oct 2025. 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-54957 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-54957/ (Markdown: https://insights.sbomify.com/CVE-2025-54957/index.md)
```

## Sources

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

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