Arm C1 Pro prior r1p2-50eac0 Memory Access race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.0$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Arm C1 Pro. The affected element is an unknown function of the component Memory Access Handler. Performing a manipulation results in race condition. This vulnerability is reported as CVE-2026-0995. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Arm C1 Pro. It has been classified as problematic. This affects an unknown code of the component Memory Access Handler. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. The impact remains unknown. The summary by CVE is:

An issue has been identified in Arm C1-Pro before r1p2-50eac0, where, under certain conditions, a TLBI+DSB might fail to ensure the completion of memory accesses related to SME.

It is possible to read the advisory at developer.arm.com. This vulnerability is uniquely identified as CVE-2026-0995 since 01/15/2026. The exploitability is told to be difficult. The technical details are unknown and an exploit is not publicly available.

Upgrading to version r1p2-50eac0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-9178). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.1
VulDB Meta Temp Score: 4.0

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

ADP CISA Base Score: 3.6
ADP CISA Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: C1 Pro r1p2-50eac0

Timelineinfo

01/15/2026 CVE reserved
03/02/2026 +46 days Advisory disclosed
03/02/2026 +0 days VulDB entry created
03/04/2026 +2 days VulDB entry last update

Sourcesinfo

Advisory: developer.arm.com
Status: Confirmed

CVE: CVE-2026-0995 (🔒)
GCVE (CVE): GCVE-0-2026-0995
GCVE (VulDB): GCVE-100-348387
EUVD: 🔒

Entryinfo

Created: 03/02/2026 16:48
Updated: 03/04/2026 01:18
Changes: 03/02/2026 16:48 (53), 03/02/2026 18:00 (1), 03/04/2026 01:18 (11)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!