CyberSecBulletin
CVE-2025-0647NVD status: Analyzed

Neoverse-N2: Sensitive Information in Resource Not Removed Before Reuse

Published Updated By the CyberSecBulletin desk

CVE-2025-0647 is a high-severity sensitive information in resource not removed before reuse vulnerability in Neoverse-N2 from Arm, with a CVSS 3.1 base score of 7.9 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. Affected Neoverse-N2 versions: 0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Neoverse-N2 you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on developer.arm.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
ArmNeoverse-N20Not stated
ArmNeoverse-V3AE0Not stated
ArmNeoverse-V30Not stated
ArmNeoverse-V20Not stated
ArmCortex-X9250Not stated
ArmCortex-X40Not stated
ArmCortex-X30Not stated
ArmCortex-X20Not stated
ArmCortex-A7100Not stated
ArmC1-Premium0Not stated
ArmC1-Ultra0Not stated
ArmC1-ultra FirmwareNot specified in the recordNot stated
ArmC1-premium FirmwareNot specified in the recordNot stated
ArmCortex-a710 FirmwareNot specified in the recordNot stated
ArmCortex-x2 FirmwareNot specified in the recordNot stated
ArmCortex-x3 FirmwareNot specified in the recordNot stated
ArmCortex-x4 FirmwareNot specified in the recordNot stated
ArmCortex-x925 FirmwareNot specified in the recordNot stated
ArmNeoverse-v2 FirmwareNot specified in the recordNot stated
ArmNeoverse-v3 FirmwareNot specified in the recordNot stated
ArmNeoverse-v3ae FirmwareNot specified in the recordNot stated
ArmNeoverse-n2 FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N. Scored by CISA (ADP).

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Sensitive Information in Resource Not Removed Before Reuse

The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or zeroize the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.

How developers prevent this class of flaw

  • During critical state transitions, information not needed in the next state should be removed or overwritten with fixed patterns (such as all 0's) or random data, before the transition to the next state.
  • Be careful using vfork() and fork() in security sensitive code. The process state will not be cleaned up and will contain traces of data from past use.

More Sensitive Information in Resource Not Removed Before Reuse vulnerabilities (CWE-226)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Neoverse-N2

All Neoverse-N2 vulnerabilities

Spotted an error? Tell us.