Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

Qualcomm

46,786 known vulnerabilities

529
CRITICAL
1,510
HIGH
426
MEDIUM

Top Products

ar8035 643 ar8035 firmware 621 aqt1000 616 mdm9206 611 mdm9206 firmware 603 aqt1000 firmware 586 mdm9607 564 mdm9607 firmware 562 mdm9650 483 mdm9650 firmware 473
2,465 CVEs · Page 11/50
8.4
CVE-2024-23383

Memory corruption when kernel driver attempts to trigger hardware fences.

8.4
CVE-2024-23382

Memory corruption while processing graphics kernel driver request to create DMA fence.

8.4
CVE-2024-23381

Memory corruption when memory mapped in a VBO is not unmapped by the GPU SMMU.

6.2
CVE-2024-23357

Transient DOS while importing a PKCS#8-encoded RSA key with zero bytes modulus.

7.8
CVE-2024-23356

Memory corruption during session sign renewal request calls in HLOS.

7.8
CVE-2024-23355

Memory corruption when keymaster operation imports a shared key.

7.5
CVE-2024-23353

Transient DOS while decoding attach reject message received by UE, when IEI is set to ESM_IEI.

7.5
CVE-2024-23352

Transient DOS when NAS receives ODAC criteria of length 1 and type 1 in registration accept OTA.

6.5
CVE-2024-23350

Permanent DOS when DL NAS transport receives multiple payloads such that one payload contains SOR container whose integr

8.4
CVE-2024-21481

Memory corruption when preparing a shared memory notification for a memparcel in Resource Manager.

7.5
CVE-2024-21479

Transient DOS during music playback of ALAC content.

6.5
CVE-2024-21467

Information disclosure while handling beacon probe frame during scan entry generation in client side.

6.5
CVE-2024-21459

Information disclosure while handling beacon or probe response frame in STA.

8.4
CVE-2024-23380

Memory corruption while handling user packets during VBO bind operation.

8.4
CVE-2024-23373

Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released.

8.4
CVE-2024-23372

Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size.

7.8
CVE-2024-23368

Memory corruption when allocating and accessing an entry in an SMEM partition.

6.8
CVE-2024-21482

Memory corruption during the secure boot process, when the `bootm` command is used, it bypasses the authentication of th

7.3
CVE-2024-21469

Memory corruption when an invoke call and a TEE call are bound for the same trusted application.

6.5
CVE-2024-21466

Information disclosure while parsing sub-IE length during new IE generation.

7.8
CVE-2024-21465

Memory corruption while processing key blob passed by the user.

7.1
CVE-2024-21462

Transient DOS while loading the TA ELF file.

8.4
CVE-2024-21461

Memory corruption while performing finish HMAC operation when context is freed by keymaster.

7.1
CVE-2024-21460

Information disclosure when ASLR relocates the IMEM and Secure DDR portions as one chunk in virtual address space.

6.5
CVE-2024-21458

Information disclosure while handling SA query action frame.

6.5
CVE-2024-21457

INformation disclosure while handling Multi-link IE in beacon frame.

6.5
CVE-2024-21456

Information Disclosure while parsing beacon frame in STA.

8.4
CVE-2023-43554

Memory corruption while processing IOCTL handler in FastRPC.

7.5
CVE-2024-23363

Transient DOS while processing an improperly formatted Fine Time Measurement (FTM) management frame.

8.4
CVE-2024-23360

Memory corruption while creating a LPAC client as LPAC engine was allowed to access GPU registers.

6.2
CVE-2024-21478

transient DOS when setting up a fence callback to free a KGSL memory entry object during DMA.

9.3
CVE-2023-43556

Memory corruption in Hypervisor when platform information mentioned is not aligned.

8.2
CVE-2023-43555

Information disclosure in Video while parsing mp2 clip with invalid section length.

9.1
CVE-2023-43551

Cryptographic issue while performing attach with a LTE network, a rogue base station can skip the authentication phase a

6.7
CVE-2023-43545

Memory corruption when more scan frequency list or channels are sent from the user space.

6.7
CVE-2023-43544

Memory corruption when IPC callback handle is used after it has been released during register callback by another thread

6.7
CVE-2023-43543

Memory corruption in Audio during a playback or a recording due to race condition between allocation and deallocation of

7.8
CVE-2023-43542

Memory corruption while copying a keyblob`s material when the key material`s size is not accurately checked.

9.3
CVE-2023-43538

Memory corruption in TZ Secure OS while Tunnel Invoke Manager initialization.

6.5
CVE-2023-43537

Information disclosure while handling T2LM Action Frame in WLAN Host.

8.4
CVE-2024-23354

Memory corruption when the IOCTL call is interrupted by a signal.

8.4
CVE-2024-23351

Memory corruption as GPU registers beyond the last protected range can be accessed through LPAC submissions.

7.3
CVE-2024-21480

Memory corruption while playing audio file having large-sized input buffer.

7.5
CVE-2024-21477

Transient DOS while parsing a protected 802.11az Fine Time Measurement (FTM) frame.

7.8
CVE-2024-21476

Memory corruption when the channel ID passed by user is not validated and further used.

7.8
CVE-2024-21475

Memory corruption when the payload received from firmware is not as per the expected protocol size.

8.4
CVE-2024-21474

Memory corruption when size of buffer from previous call is used without validation or re-initialization.

8.4
CVE-2024-21471

Memory corruption when IOMMU unmap of a GPU buffer fails in Linux.

8.4
CVE-2023-43531

Memory corruption while verifying the serialized header when the key pairs are generated.

5.9
CVE-2023-43530

Memory corruption in HLOS while checking for the storage type.

Frequently Asked Questions

How many CVEs affect Qualcomm?

Qualcomm has 46,786 CVE records in our database, including 9787 critical and 28782 high severity vulnerabilities. 12 of these are listed in CISA's Known Exploited Vulnerabilities catalog.

What are the most severe Qualcomm vulnerabilities?

Qualcomm has 9787 critical severity (CVSS 9.0+) and 28782 high severity (CVSS 7.0-8.9) vulnerabilities. 12 vulnerabilities are confirmed as actively exploited in the wild.

How can I scan for Qualcomm vulnerabilities?

CyberStrike's AI-powered security agents automatically detect vulnerabilities in Qualcomm products across your infrastructure. The platform provides continuous pentesting, DAST scanning, and real-time vulnerability monitoring with actionable remediation guidance.

Detect Qualcomm Vulnerabilities

CyberStrike scans your infrastructure for Qualcomm vulnerabilities and provides real-time remediation guidance.

Get Started