CVE-2017-8244

low-risk
Published 2017-05-12

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).

Do I need to act?

-
0.03% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.0/10 High
LOCAL / HIGH complexity

Affected Products (1)

Affected Vendors

Google

References (6)

Third Party Advisory http://www.securityfocus.com/bid/98547
Vendor Advisory https://source.android.com/security/bulletin/pixel/2017-12-01
Broken Link https://www.codeaurora.org/buffer-overflow-msmvidc-debugfs-driver-coreinforead-a...
Third Party Advisory http://www.securityfocus.com/bid/98547
Vendor Advisory https://source.android.com/security/bulletin/pixel/2017-12-01
Broken Link https://www.codeaurora.org/buffer-overflow-msmvidc-debugfs-driver-coreinforead-a...
23
/ 100
low-risk
Severity 18/34 · Moderate
Exploitability 0/34 · Minimal
Exposure 5/34 · Minimal