Failure to initialize the extra buffer can lead to an out of buffer access in WLAN function in Snapdragon Auto, Snapdragon Compute, Snapdra…
Failure to initialize the extra buffer can lead to an out of buffer access in WLAN function in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCS605, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 712 / SD 710 / SD 670, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM630, SDM660, SDX20, SDX24
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
https://cwe.mitre.org/data/definitions/665.html →Open in CWE collection →The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
https://capec.mitre.org/data/definitions/26.html →Open in CAPEC collection →This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
https://capec.mitre.org/data/definitions/29.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| mdm9150_firmware | * | Tracked |
| mdm9206_firmware | * | Tracked |
| mdm9607_firmware | * | Tracked |
| mdm9640_firmware | * | Tracked |
| mdm9650_firmware | * | Tracked |
| msm8996au_firmware | * | Tracked |
| qcs605_firmware | * | Tracked |
| sd_425_firmware | * | Tracked |
| sd_427_firmware | * | Tracked |
| sd_430_firmware | * | Tracked |
| sd_435_firmware | * | Tracked |
| sd_450_firmware | * | Tracked |
| sd_625_firmware | * | Tracked |
| sd_636_firmware | * | Tracked |
| sd_670_firmware | * | Tracked |
| sd_710_firmware | * | Tracked |
| sd_712_firmware | * | Tracked |
| sd_820a_firmware | * | Tracked |
| sd_835_firmware | * | Tracked |
| sd_845_firmware | * | Tracked |