# CVE-2022-33275: Improper validation of array index in WLAN HAL

> An attacker can exploit improper array index validation in the WLAN HAL to cause memory corruption, potentially leading to code execution or privilege escalation on Qualcomm Snapdragon devices.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2023
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-jv4q-hvqc-9497

## What is CVE-2022-33275?

CVE-2022-33275 is a high-severity memory corruption vulnerability in Qualcomm 315 5g Iot Modem Firmware, published on 5 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption due to improper validation of array index in WLAN HAL when received lm_itemNum is out of range.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2022-33275?

It affects 259 products.


Products: Qualcomm 315 5g Iot Modem Firmware, Qualcomm Apq5053-Aa Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Flight Rb5 5g Platform Firmware, Qualcomm Immersive Home 214 Platform Firmware, Qualcomm Immersive Home 216 Platform Firmware, Qualcomm Immersive Home 316 Platform Firmware, Qualcomm Immersive Home 318 Platform Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4028 Firmware, Qualcomm Ipq4029 Firmware, Qualcomm Ipq5010 Firmware, Qualcomm Ipq5028 Firmware, Qualcomm Ipq6000 Firmware and 239 more.

## How do I fix CVE-2022-33275?

No fix has been published for CVE-2022-33275 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-33275 being exploited?

There is no known exploitation of CVE-2022-33275 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm 315 5g Iot Modem Firmware

- [CVE-2023-33107](https://insights.sbomify.com/CVE-2023-33107/): Qualcomm Multiple Chipsets Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2023-33063](https://insights.sbomify.com/CVE-2023-33063/): Qualcomm Multiple Chipsets Use-After-Free (high 7.8, exploited in the wild)
- [CVE-2025-27034](https://insights.sbomify.com/CVE-2025-27034/): Improper Validation of Array Index in Multi-Mode Call Processor (critical 9.8)
- [CVE-2023-22388](https://insights.sbomify.com/CVE-2023-22388/): Use of Out-of-range Pointer Offset in Multi-mode Call Processor (critical 9.8)
- [CVE-2023-28578](https://insights.sbomify.com/CVE-2023-28578/): Improper Input Validation in Services (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-33275 and fix it if it is affected.

What it is: CVE-2022-33275 is a high-severity memory corruption vulnerability in Qualcomm 315 5g Iot Modem Firmware, published on 5 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-33275 in the wild and no public exploit code.

Affected product: Qualcomm 315 5g Iot Modem Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-33275/ (Markdown: https://insights.sbomify.com/CVE-2022-33275/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-33275
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-33275
- OSV: https://osv.dev/vulnerability/CVE-2022-33275

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-33275/
Summaries are generated and may contain mistakes; the official description above is the record.