215 Mobile vulnerabilitiesRanked by how likely they are to be used.
215 Mobile is made by Qualcomm. We track 15 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Qualcomm lists newer releases under their own names, such as 215 Mobile Firmware, so check those pages too.
We keep watching the known-exploited list.
Is 215 Mobile listed under other names? Yes.
Qualcomm also lists 215 Mobile under more specific names, such as 215 Mobile Firmware and 215 Mobile Platform. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which 215 Mobile vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of 215 Mobile's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which 215 Mobile flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.3%CVE-2023-43551Critical
Cryptographic issue while performing attach with a LTE network, a rogue base station can skip the authentication phase and immediately send the Security Mode Command.
- 0.2%CVE-2025-21427High
Information disclosure while decoding this RTP packet Payload when UE receives the RTP packet from the network.
- 0.2%CVE-2023-43555High
Information disclosure in Video while parsing mp2 clip with invalid section length.
- 0.2%CVE-2024-33060High
Memory corruption when two threads try to map and unmap a single node simultaneously.
- 0.1%CVE-2024-33052High
Memory corruption when user provides data for FM HCI command control operations.
- 0.1%CVE-2023-28547High
Memory corruption in SPS Application while requesting for public key in sorter TA.
- 0.1%CVE-2023-33023High
Memory corruption while processing finish_sign command to pass a rsp buffer.
- 0.1%CVE-2023-33066High
Memory corruption in Audio while processing RT proxy port register driver.
- 0.1%CVE-2024-21468High
Memory corruption when there is failed unmap operation in GPU.
- 0.1%CVE-2024-21471High
Memory corruption when IOMMU unmap of a GPU buffer fails in Linux.
Running 215 Mobile? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Cryptographic issue while performing attach with a LTE network, a rogue base station can skip the authentication phase and immediately send the Security Mode Command.
- Matched to
- 215 Mobile on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 15 published vulnerabilities listed under the name 215 Mobile, across 0 versions.
None of 215 Mobile's vulnerabilities is on the list of flaws known to be exploited today.
Qualcomm also lists 215 Mobile under more specific names, such as 215 Mobile Firmware and 215 Mobile Platform. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track 215 Mobile. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.