# CVE-2023-33107: Qualcomm Multiple Chipsets Integer Overflow

> An integer overflow in Qualcomm Graphics Linux allows memory corruption during IOCTL calls, potentially enabling code execution or privilege escalation on Android 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:** Yes, since 5 Dec 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2023
- **Updated:** 21 Oct 2025
- **Also known as:** 3611296, A-299649795, ASB-A-299649795, GHSA-wg3g-ggh3-7wgp

## What is CVE-2023-33107?

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

### Official description

Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-33107?

It affects 242 products.


Products: Qualcomm 315 5g Iot Modem Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm C-V2x 9150 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Flight Rb5 5g Platform Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8108 Firmware, Qualcomm Msm8209 Firmware and 222 more.

## How do I fix CVE-2023-33107?

Apply the vendor's patch. US federal agencies must fix it by 26 Dec 2023.

## Is CVE-2023-33107 being exploited?

Yes. Attackers have exploited CVE-2023-33107 in the wild since at least 5 Dec 2023.

Public exploit code:

- full exploit code (github_poc): https://github.com/keto0422/CVE-2023-33107
- A kernel exploit for Pico 4 devices based on cve-2023-33107.  (github_poc): https://github.com/264312431/picohaxx

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

- [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)
- [CVE-2023-33072](https://insights.sbomify.com/CVE-2023-33072/): Buffer copy without checking size of Input in Core (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33107 and fix it if it is affected.

What it is: CVE-2023-33107 is a high-severity vulnerability in Qualcomm 315 5g Iot Modem Firmware, published on 5 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-33107 in the wild since at least 5 Dec 2023.

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-2023-33107/ (Markdown: https://insights.sbomify.com/CVE-2023-33107/index.md)
```

## Sources

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

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