205 Mobile Platform vulnerabilitiesRanked by how likely they are to be used.
205 Mobile Platform is made by Qualcomm. We track 10 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 205 Mobile Platform Firmware, so check those pages too.
We keep watching the known-exploited list.
Is 205 Mobile Platform listed under other names? Yes.
Qualcomm also lists 205 Mobile Platform under more specific names, such as 205 Mobile Platform Firmware. 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 205 Mobile Platform vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of 205 Mobile Platform's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which 205 Mobile Platform 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-2024-23359High
Information disclosure while decoding Tracking Area Update Accept or Attach Accept message received from network.
- 0.3%CVE-2024-23358High
Transient DOS when registration accept OTA is received with incorrect ciphering key data IE in Modem.
- 0.3%CVE-2024-23385High
Transient DOS as modem reset occurs when an unexpected MAC RAR (with invalid PDU length) is seen at UE.
- 0.1%CVE-2024-23373High
Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released.
- 0.1%CVE-2024-33056High
Memory corruption when allocating and accessing an entry in an SMEM partition continuously.
- 0.1%CVE-2024-43052High
Memory corruption while processing API calls to NPU with invalid input.
- 0.1%CVE-2024-38422High
Memory corruption while processing voice packet with arbitrary data received from ADSP.
- 0.1%CVE-2024-38423High
Memory corruption while processing GPU page table switch.
- <0.1%CVE-2024-33027High
Memory corruption can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table.
- <0.1%CVE-2024-33043Medium
Transient DOS while handling PS event when Program Service name length offset value is set to 255.
Running 205 Mobile Platform? 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
Information disclosure while decoding Tracking Area Update Accept or Attach Accept message received from network.
- Matched to
- 205 Mobile Platform 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 10 published vulnerabilities listed under the name 205 Mobile Platform, across 0 versions.
None of 205 Mobile Platform's vulnerabilities is on the list of flaws known to be exploited today.
Qualcomm also lists 205 Mobile Platform under more specific names, such as 205 Mobile Platform Firmware. 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 205 Mobile Platform. 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.