How severe is CVE-2025-0647?

CVE-2025-0647 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-0647 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-0647?

CVE-2025-0647 primarily affects Arm C1-ultra Firmware. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-0647?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-0647 have an EU (EUVD) identifier?

Yes. CVE-2025-0647 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-2516.

When was CVE-2025-0647 published?

CVE-2025-0647 was published on 2026-01-14 and last updated on 2026-06-17.

CVE-2025-0647

CVE-2025-0647 is a high-severity vulnerability in Arm C1-ultra Firmware with a CVSS 3.x base score of 7.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-226.

Key facts

Severity: High (CVSS 3.x base score 7.9)
EPSS exploit prediction: 0% (5th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-2516
Weakness: CWE-226
Affected product: Arm C1-ultra Firmware
Published: 2026-01-14
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-0647?: 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.
How severe is CVE-2025-0647?: CVE-2025-0647 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-0647 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-0647?: CVE-2025-0647 primarily affects Arm C1-ultra Firmware. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-0647?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-0647 have an EU (EUVD) identifier?: Yes. CVE-2025-0647 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-2516.
When was CVE-2025-0647 published?: CVE-2025-0647 was published on 2026-01-14 and last updated on 2026-06-17.

References

Affected products (11)

cpe:2.3:o:arm:c1-ultra_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:c1-premium_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:cortex-a710_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:cortex-x2_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:cortex-x3_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:cortex-x4_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:cortex-x925_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:neoverse-v2_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:neoverse-v3_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:neoverse-v3ae_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:arm:neoverse-n2_firmware:-:*:*:*:*:*:*:*

More vulnerabilities in Arm C1-ultra Firmware

CVE-2024-7881 — Medium (CVSS 5.1): An unprivileged context can trigger a data memory-dependent prefetch engine to fetch the contents of a privileged…

All CVEs affecting Arm C1-ultra Firmware →

Other CWE-226 vulnerabilities

CVE-2019-25560 — High (CVSS 7.5): Lyric Video Creator 2.1 contains a denial of service vulnerability that allows attackers to crash the application by…
CVE-2023-41138 — High (CVSS 7.5): The AppsAnywhere macOS client-privileged helper can be tricked into executing arbitrary commands with elevated…
CVE-2026-5795 — High (CVSS 7.4): In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal…
CVE-2026-32960 — Medium (CVSS 6.5): SD-330AC and AMC Manager provided by silex technology, Inc. contain an issue with a sensitive information in resource…
CVE-2025-2522 — Medium (CVSS 6.5): The Honeywell Experion PKS and OneWireless WDM contains Sensitive Information in Resource vulnerability in the…
CVE-2025-11602 — Medium (CVSS 6.3): Potential information leak in bolt protocol handshake in Neo4j Enterprise and Community editions allows attacker to…

Browse all CWE-226 vulnerabilities →