In multiple locations, there is a possible way to conduct local privilege escalation 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-26923US | medium4.7 | — | ||
In the Linux kernel, the following vulnerability has been resolved:
af_unix: Fix garbage collector racing against connect()
Garbage collector does not take into account the risk… | ||||
02
references
External citations — patches, advisories, analysis.
- https://android.googlesource.com/kernel/common/+/65e0a92c6d27d4cbaa0deef668df12b69853d65eFIX
- https://android.googlesource.com/kernel/common/+/94c88f80ffddff00f0af448c02dfd8a3f3cdd692FIX
- https://android.googlesource.com/kernel/common/+/d0c6724b0f6fa713e7fcfc0eb0173625519ba570FIX
- https://android.googlesource.com/kernel/common/+/e8e652b8c81afc06e9bc801f6eb4896516be2d62FIX
- https://source.android.com/security/bulletin/2024-07-01ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan