Possible out of bound array access as there is no check on carrier index passed in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCM2150, QCS605, QM215, Rennell, SC7180, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130
Summary
AIAffected Snapdragon products may access an array out of bounds because the carrier index is not checked. The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Who should check
Engineers using Snapdragon Auto, Compute, Consumer IOT, Industrial IOT, Mobile, or Wearables with the listed affected chipsets should check; affected software versions are not specified.
What to do
- 1Consult the Qualcomm vendor advisory for affected configurations and fixes.