# CVE-2025-50897: Denial of service in n/a

> A flaw in the BOOMv1.2 processor's memory management unit causes unexpected kernel panics during valid store operations, leading to denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-rm2f-5xvp-f49w

## What is CVE-2025-50897?

CVE-2025-50897 is a medium-severity denial of service vulnerability in n/a, published on 19 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability exists in riscv-boom SonicBOOM 1.2 (BOOMv1.2) processor implementation, where valid virtual-to-physical address translations configured with write permissions (PTE_W) in SV39 mode may incorrectly trigger a Store/AMO access fault during store instructions (sd). This occurs despite the presence of proper page table entries and valid memory access modes. The fault is reproducible when transitioning into virtual memory and attempting store operations in mapped kernel memory, indicating a potential flaw in the MMU, PMP, or memory access enforcement logic. This may cause unexpected kernel panics or denial of service in systems using BOOMv1.2.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Boom-Core Boomv.

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

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

## Is CVE-2025-50897 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50897 is a medium-severity denial of service vulnerability in n/a, published on 19 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50897 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-50897/ (Markdown: https://insights.sbomify.com/CVE-2025-50897/index.md)
```

## Sources

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

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