# CVE-2023-43513: Use of Out-of-range Pointer Offset in PCIe

> An attacker can exploit an out-of-range pointer offset in Qualcomm Snapdragon PCIe drivers to cause memory corruption, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2024
- **Updated:** 16 Jun 2025
- **Also known as:** 3545432, A-303101658, ASB-A-303101658, GHSA-pg26-49x3-7h59

## What is CVE-2023-43513?

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

### Official description

Memory corruption while processing the event ring, the context read pointer is untrusted to HLOS and when it is passed with arbitrary values, may point to address in the middle of ring element.

Weakness: CWE-787 (Out-of-bounds Write), CWE-823 (Use of Out-of-range Pointer Offset)

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

It affects 267 products.


Products: Qualcomm 315 5g Iot Modem Firmware, Qualcomm Apq8017 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 Fsm20055 Firmware, Qualcomm Fsm20056 Firmware, Qualcomm Immersive Home 214 Platform Firmware, Qualcomm Immersive Home 216 Platform Firmware, Qualcomm Immersive Home 316 Platform Firmware and 247 more.

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

Apply the vendor's patch.

## Is CVE-2023-43513 being exploited?

There is no known exploitation of CVE-2023-43513 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-2023-43513 and fix it if it is affected.

What it is: CVE-2023-43513 is a high-severity memory corruption vulnerability in Qualcomm 315 5g Iot Modem Firmware, published on 6 Feb 2024. 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-2023-43513 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-2023-43513/ (Markdown: https://insights.sbomify.com/CVE-2023-43513/index.md)
```

## Sources

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

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