CVE Intelligence
Skip to main content
HIGH

CVE-2025-0647

CVE-2025-0647 Vulnerability Analysis & Exploit Intelligence

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.

Published Updated Sources: cvelistV5, Arm

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

arm

11 products listed

CVSS base

7.9

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

arm

Products (11)

neoverse n2neoverse v3aeneoverse v3neoverse v2cortex x925cortex x4cortex x3cortex x2cortex a710c1 premiumc1 ultra

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.9CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-226

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1005Data from Local System
  • T1552.004Unsecured Credentials: Private Keys

References

2 on the record

Elsewhere on this site

  • armevery CVE for this vendor
  • CWE-226other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.