CVE-2019-10524

Name of the Vulnerable Software and Affected Versions Qualcomm Snapdragon Auto versions (affected versions not specified) Qualcomm Snapdragon Consumer IOT versions (affected versions not specified) Qualcomm Snapdragon Industrial IOT versions (affected versions not specified) Qualcomm Snapdragon Mobile versions (affected versions not specified) Qualcomm Snapdragon Voice & Music versions (affected versions not specified) Qualcomm Snapdragon Wearables versions (affected versions not specified) MDM9150 (affected versions not specified) MDM9206 (affected versions not specified) MDM9607 (affected versions not specified) MDM9640 (affected versions not specified) MDM9650 (affected versions not specified) MSM8909W (affected versions not specified) MSM8996AU (affected versions not specified) QCS405 (affected versions not specified) QCS605 (affected versions not specified) Qualcomm 215 (affected versions not specified) SD 210/SD 212/SD 205 (affected versions not specified) SD 425 (affected versions not specified) SD 427 (affected versions not specified) SD 430 (affected versions not specified) SD 435 (affected versions not specified) SD 439 / SD 429 (affected versions not specified) SD 450 (affected versions not specified) SD 625 (affected versions not specified) SD 632 (affected versions not specified) SD 636 (affected versions not specified) SD 665 (affected versions not specified) SD 675 (affected versions not specified) SD 712 / SD 710 / SD 670 (affected versions not specified) SD 730 (affected versions not specified) SD 820 (affected versions not specified) SD 820A (affected versions not specified) SD 835 (affected versions not specified) SD 845 / SD 850 (affected versions not specified) SD 855 (affected versions not specified) SDA660 (affected versions not specified) SDM439 (affected versions not specified) SDM630 (affected versions not specified) SDM660 (affected versions not specified) SDX20 (affected versions not specified) SDX24 (affected versions not specified)

Description The issue is related to a lack of check for a negative value returned for get clk, which is wrongly interpreted as a valid pointer. This leads to a use-after-free condition in the clk driver. The estimated number of potentially affected devices worldwide is not specified. There is no information about real-world incidents where this issue was exploited.

Recommendations At the moment, there is no information about a newer version that contains a fix for this vulnerability.