# CVE-2025-67749: PCSX2 has an Out-of-bounds Read due to unchecked offset and size passed to memcpy

> A specially crafted disc image or ELF can cause an out-of-bounds read in PCSX2, allowing attackers to read data from emulator memory.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-67749, GHSA-69wg-97fx-8j5w, UBUNTU-CVE-2025-67749

## What is CVE-2025-67749?

CVE-2025-67749 is a medium-severity memory corruption vulnerability in pcsx2, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PCSX2 is a free and open-source PlayStation 2 (PS2) emulator. In versions 2.5.377 and below, an unchecked offset and size used in a memcpy operation inside PCSX2's CDVD SCMD 0x91 and SCMD 0x8F handlers allow a specially crafted disc image or ELF to cause an out-of-bounds read from emulator memory. Because the offset and size is controlled through MG header fields, a specially crafted ELF can read data beyond the bounds of mg_buffer and have it reflected back into emulated memory. This issue is fixed in version 2.5.378.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2025-67749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67749 is a medium-severity memory corruption vulnerability in pcsx2, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-67749 in the wild and no public exploit code.

Affected product: pcsx2. 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-67749/ (Markdown: https://insights.sbomify.com/CVE-2025-67749/index.md)
```

## Sources

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

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