Multiple Read overflows issue due to improper length check while decoding tau reject/tau accept/detach request/attach reject/attach accept in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9205, MDM9206, MDM9607, MDM9615, 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
AIImproper length checks can cause out-of-bounds reads while affected Snapdragon products decode TAU, detach, or attach messages. The input does not specify the attacker’s access requirements, whether authentication or user interaction is needed, or the resulting impact beyond the reads.
Who should check
Engineers using the listed Snapdragon Auto, Compute, Consumer IOT, Industrial IOT, Mobile, or Wearables products on the identified chipsets should check their exposure; affected software versions are not specified.
What to do
- 1Consult the Qualcomm vendor advisory for affected software and fixes.
- 2Apply the applicable vendor-provided update.