Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Android | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Android |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.102% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-453 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Security Coprocessor Execution from Non‑Secure Memory | |
| Weaknesses | CWE-284 CWE-665 |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Security Coprocessor Execution from Non‑Secure Memory | |
| Weaknesses | CWE-284 CWE-665 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In multiple functions of mpu.c, there is a possible way to execute code from non-secure memory in the security coprocessor due to an insecure default value. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|