CVE-2024-7881: An unprivileged context can trigger a data memory-dependent prefetch engine to fetch the contents of a privileged location and consume those…
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: arm-trusted-firmware (Debian:13) 2.12.1+dfsg-1.
Low priority for now. Upgrade to arm-trusted-firmware (Debian:13) 2.12.1+dfsg-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 28, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-203
Report tools
Action score
20
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| arm | c1-premium firmware | cpe:2.3:o:arm:c1-premium_firmware |
| arm | c1-premium | cpe:2.3:h:arm:c1-premium |
| arm | c1-pro firmware | cpe:2.3:o:arm:c1-pro_firmware |
| arm | c1-pro | cpe:2.3:h:arm:c1-pro |
| arm | c1-ultra firmware | cpe:2.3:o:arm:c1-ultra_firmware |
| arm | c1-ultra | cpe:2.3:h:arm:c1-ultra |
| arm | cortex-x3 firmware | cpe:2.3:o:arm:cortex-x3_firmware |
| arm | cortex-x3 | cpe:2.3:h:arm:cortex-x3 |
| arm | cortex-x4 firmware | cpe:2.3:o:arm:cortex-x4_firmware |
| arm | cortex-x4 | cpe:2.3:h:arm:cortex-x4 |
| arm | cortex-x925 firmware | cpe:2.3:o:arm:cortex-x925_firmware |
| arm | cortex-x925 | cpe:2.3:h:arm:cortex-x925 |
and 6 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Arm). Independent of NVD's CPE analysis and usually ahead of it.
Arm C1-Premium
- 0affected
Arm C1-Pro
- 0affected
Arm C1-Ultra
- 0affected
Arm Cortex-X3
- 0affected
Arm Cortex-X4
- 0affected
Arm Cortex-X925
- 0affected
Arm Neoverse V2
- 0affected
Arm Neoverse V3
- 0affected
Arm Neoverse V3AE
- 0affected
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arm c1-premium firmwareall versions
- arm c1-pro firmwareall versions
- arm c1-ultra firmwareall versions
- arm cortex-x3 firmwareall versions
- arm cortex-x4 firmwareall versions
- arm cortex-x925 firmwareall versions
- arm neoverse-v2 firmwareall versions
- arm neoverse-v3 firmwareall versions
- arm neoverse-v3ae firmwareall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | arm-trusted-firmware | from 0 | — |
| Debian:13 | arm-trusted-firmware | before 2.12.1+dfsg-1 | 2.12.1+dfsg-1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:arm-trusted-firmware | 2.12.1+dfsg-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.