# CVE-2024-7881: Information disclosure in C1-Premium

> An unprivileged context can exploit a prefetch engine to read privileged memory contents, potentially leaking sensitive data.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2025
- **Updated:** 18 Nov 2025
- **Also known as:** A-361573291, ASB-A-361573291, DEBIAN-CVE-2024-7881, GHSA-75fm-2jm9-p338, OESA-2025-1342, OESA-2025-1343, OESA-2025-1344, OESA-2025-1345, UBUNTU-CVE-2024-7881

## What is CVE-2024-7881?

CVE-2024-7881 is a medium-severity vulnerability in Arm C1-Premium, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An unprivileged context can trigger a data
memory-dependent prefetch engine to fetch the contents of a privileged location
and consume those contents as an address that is also dereferenced.

Weakness: CWE-203 (Observable Discrepancy), CWE-1422 (Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution)

## Which versions are affected by CVE-2024-7881?

It affects 9 products.


Products: Arm C1-Premium Firmware, Arm C1-Pro Firmware, Arm C1-Ultra Firmware, Arm Cortex-X3 Firmware, Arm Cortex-X4 Firmware, Arm Cortex-X925 Firmware, Arm Neoverse-V2 Firmware, Arm Neoverse-V3 Firmware, Arm Neoverse-V3ae Firmware.

## How do I fix CVE-2024-7881?

Apply the vendor's patch.

## Is CVE-2024-7881 being exploited?

There is no known exploitation of CVE-2024-7881 in the wild and no public exploit code.

## Other vulnerabilities in Arm C1-Premium

- [CVE-2025-0647](https://insights.sbomify.com/CVE-2025-0647/): Other in C1-Premium (high 7.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7881 and fix it if it is affected.

What it is: CVE-2024-7881 is a medium-severity vulnerability in Arm C1-Premium, published on 28 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7881 in the wild and no public exploit code.

Affected product: Arm C1-Premium. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-7881/ (Markdown: https://insights.sbomify.com/CVE-2024-7881/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7881
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7881
- OSV: https://osv.dev/vulnerability/CVE-2024-7881

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-7881/
Summaries are generated and may contain mistakes; the official description above is the record.