# CVE-2025-0647: Other in C1-Premium

> Attackers can exploit stale TLB entries in specific Arm CPUs to bypass memory isolation, potentially reading sensitive data or circumventing security controls.

- **Severity:** High 7.9 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-0647, GHSA-xxhx-7292-7rv8

## What is CVE-2025-0647?

CVE-2025-0647 is a high-severity vulnerability in Arm C1-Premium, published on 14 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In certain Arm CPUs, a CPP RCTX instruction executed on one Processing Element (PE) may inhibit TLB invalidation when a TLBI is issued to the PE, either by the same PE or another PE in the shareability domain. In this case, the PE may retain stale TLB entries which should have been invalidated by the TLBI.

Weakness: CWE-226 (Sensitive Information in Resource Not Removed Before Reuse)

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

It affects 11 products.


Products: Arm C1-Premium Firmware, Arm C1-Ultra Firmware, Arm Cortex-A710 Firmware, Arm Cortex-X2 Firmware, Arm Cortex-X3 Firmware, Arm Cortex-X4 Firmware, Arm Cortex-X925 Firmware, Arm Neoverse-N2 Firmware, Arm Neoverse-V2 Firmware, Arm Neoverse-V3 Firmware, Arm Neoverse-V3ae Firmware.

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

Apply the vendor's patch.

## Is CVE-2025-0647 being exploited?

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

## Other vulnerabilities in Arm C1-Premium

- [CVE-2024-7881](https://insights.sbomify.com/CVE-2024-7881/): Information disclosure in C1-Premium (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0647 is a high-severity vulnerability in Arm C1-Premium, published on 14 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0647 in the wild and no public exploit code.

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

## Sources

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

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