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.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.119% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-119 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Android Kernel Heap Corruption During Thread Creation Leads to Local Privilege Escalation | |
| Weaknesses | CWE-122 CWE-269 |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Android Kernel Heap Corruption During Thread Creation Leads to Local Privilege Escalation | |
| Weaknesses | CWE-122 CWE-269 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
No data.