Lack of check for a negative value returned for get_clk is wrongly interpreted as valid pointer and lead to use after free in clk driver in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20, SDX24
This is a vulnerability exploitable with only local access requires the attacker to have either
physical access to the vulnerable system or a local (shell) account. Examples of locally
exploitable vulnerabilities are peripheral attacks such as Firewire/USB DMA attacks, and
local privilege escalations (e.g., sudo).
Specialized access conditions or extenuating circumstances do not exist. The following are examples:
The affected product typically requires access to a wide range of systems and users, possibly anonymous an untrusted (e.g., Internet-facing web or mail server).
The affected configuration is default or ubiquitous. The attack can be performed manually and requires little skill or additional information gathering.
The 'race condition' is a lazy one (i.e., it is technically a race but easily winnable).
Authentication is not required to access and exploit the vulnerability.
There is considerable informational disclosure. Access to some system files is
possible, but the attacker does not have control over what is obtained, or the scope of
the loss is constrained. An example is a vulnerability that divulges only certain tables
in a database.
Modification of some system files or information is possible, but the attacker does not
have control over what can be modified, or the scope of what the attacker can affect is
limited. For example, system or application files may be overwritten or modified, but
either the attacker has no control over which files are affected or the attacker can
modify files within only a limited context or scope.
There is reduced performance or interruptions in resource availability. An example is
a network-based flood attack that permits a limited number of successful connections
to an Internet service.