# CVE-2025-63384: Privilege escalation in n/a

> The SRET instruction fails to downgrade privilege levels, allowing code to remain in Machine-mode instead of Supervisor-mode, enabling privilege escalation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-g435-j3hg-9vfh

## What is CVE-2025-63384?

CVE-2025-63384 is a medium-severity vulnerability in n/a, published on 10 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was discovered in RISC-V Rocket-Chip v1.6 and before implementation where the SRET (Supervisor-mode Exception Return) instruction fails to correctly transition the processor's privilege level. Instead of downgrading from Machine-mode (M-mode) to Supervisor-mode (S-mode) as specified by the sstatus.SPP bit, the processor incorrectly remains in M-mode, leading to a critical privilege retention vulnerability.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Chipsalliance Rocketchip.

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

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

## Is CVE-2025-63384 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63384 is a medium-severity vulnerability in n/a, published on 10 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63384 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-63384/ (Markdown: https://insights.sbomify.com/CVE-2025-63384/index.md)
```

## Sources

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

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