Description
In core_info_read and inst_info_read in all Android releases from CAF using the Linux kernel, variable "dbg_buf", "dbg_buf->curr" and "dbg_buf->filled_size" could be modified by different threads at the same time, but they are not protected with mutex or locks. Buffer overflow is possible on race conditions. "buffer->curr" itself could also be overwritten, which means that it may point to anywhere of kernel memory (for write).
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2017-17206 | In core_info_read and inst_info_read in all Android releases from CAF using the Linux kernel, variable "dbg_buf", "dbg_buf->curr" and "dbg_buf->filled_size" could be modified by different threads at the same time, but they are not protected with mutex or locks. Buffer overflow is possible on race conditions. "buffer->curr" itself could also be overwritten, which means that it may point to anywhere of kernel memory (for write). |
References
History
No history.
Status: PUBLISHED
Assigner: qualcomm
Published:
Updated: 2024-08-05T16:27:22.879Z
Reserved: 2017-04-25T00:00:00.000Z
Link: CVE-2017-8244
No data.
Status : Modified
Published: 2017-05-12T20:29:00.313
Modified: 2026-05-13T00:24:29.033
Link: CVE-2017-8244
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD