# CVE-2025-29364: Memory corruption in n/a

> A buffer overflow in the SPIM simulator allows attackers to bypass memory checks and potentially execute arbitrary code or escalate privileges.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2025
- **Updated:** 28 Aug 2025
- **Also known as:** DEBIAN-CVE-2025-29364, GHSA-m257-mjqp-xq37, UBUNTU-CVE-2025-29364

## What is CVE-2025-29364?

CVE-2025-29364 is a medium-severity memory corruption vulnerability in n/a, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

spimsimulator spim v9.1.24 and before is vulnerable to Buffer Overflow in the READ_SYSCALL and WRITE_SYSCALL system calls. The application verifies the legitimacy of the starting and ending addresses for memory read/write operations. By configuring the starting and ending addresses for memory read/write to point to distinct memory segments within the virtual machine, it is possible to circumvent these checks.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Spimsimulator Spim.

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

No fix has been published for CVE-2025-29364 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-29364 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29364 exists.

## Other vulnerabilities in n/a

- [CVE-2025-29365](https://insights.sbomify.com/CVE-2025-29365/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29364 is a medium-severity memory corruption vulnerability in n/a, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29364 exists.

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

## Sources

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

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