| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Arm Neoverse V2, Neoverse V3, Neoverse V3AE, Cortex-X3, Cortex-X4 and Cortex-X925. Impacted is an unknown function. Performing a manipulation results in value delimiter. This vulnerability is known as CVE-2024-7881. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in Arm Neoverse V2, Neoverse V3, Neoverse V3AE, Cortex-X3, Cortex-X4 and Cortex-X925. This affects some unknown functionality. The manipulation with an unknown input leads to a value delimiter vulnerability. CWE is classifying the issue as CWE-142. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as value delimiters when they are sent to a downstream component. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The advisory is shared at developer.arm.com. This vulnerability is uniquely identified as CVE-2024-7881 since 08/16/2024. The exploitability is told to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1944). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Google Android
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.5VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Value delimiterCWE: CWE-142 / CWE-140 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/16/2024 🔍01/28/2025 🔍
01/28/2025 🔍
12/18/2025 🔍
Sources
Advisory: developer.arm.comStatus: Confirmed
CVE: CVE-2024-7881 (🔍)
GCVE (CVE): GCVE-0-2024-7881
GCVE (VulDB): GCVE-100-293925
CERT Bund: WID-SEC-2025-1944 - Android Patchday September 2025: Multiple Vulnerabilities
Entry
Created: 01/28/2025 16:22Updated: 12/18/2025 23:50
Changes: 01/28/2025 16:22 (50), 09/07/2025 18:09 (7), 12/18/2025 23:50 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.