CVE-2017-8246
In function msm_pcm_playback_close() in all Android releases from CAF using the Linux kernel, prtd is assigned substream->runtime->private_data.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.17%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
In function msm_pcm_playback_close() in all Android releases from CAF using the Linux kernel, prtd is assigned substream->runtime->private_data. Later, prtd is freed. However, prtd is not sanitized and set to NULL, resulting in a dangling pointer. There are other functions that access the same memory (substream->runtime->private_data) with a NULL check, such as msm_pcm_volume_ctl_put(), which means this freed memory could be used.
- CVSS 3.1
- 7.8 HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.17% probability · 7th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-416
- Affected
- google/android
- Source
- product-security@qualcomm.com
References
- https://source.android.com/security/bulletin/2017-07-01Vendor Advisory
- https://www.codeaurora.org/use-after-free-alsa-pcm-playback-kernel-module-cve-2017-8246Broken Link
- https://source.android.com/security/bulletin/2017-07-01Vendor Advisory
- https://www.codeaurora.org/use-after-free-alsa-pcm-playback-kernel-module-cve-2017-8246Broken Link
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.