Vulnerabilities > Qualcomm
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-12-02 | CVE-2024-33063 | Integer Overflow or Wraparound vulnerability in Qualcomm products Transient DOS while parsing the ML IE when a beacon with common info length of the ML IE greater than the ML IE inside which this element is present. | 7.5 |
2024-12-02 | CVE-2024-43048 | Out-of-bounds Write vulnerability in Qualcomm products Memory corruption when invalid input is passed to invoke GPU Headroom API call. | 7.8 |
2024-12-02 | CVE-2024-43050 | Out-of-bounds Write vulnerability in Qualcomm products Memory corruption while invoking IOCTL calls from user space to issue factory test command inside WLAN driver. | 7.8 |
2024-12-02 | CVE-2024-43052 | Unspecified vulnerability in Qualcomm products Memory corruption while processing API calls to NPU with invalid input. | 7.8 |
2024-11-26 | CVE-2016-10408 | Unspecified vulnerability in Qualcomm products QSEE will randomly experience a fatal error during execution due to speculative instruction fetches from device memory. | 7.8 |
2024-11-26 | CVE-2017-18306 | Use of Uninitialized Resource vulnerability in Qualcomm products Information disclosure due to uninitialized variable. | 5.5 |
2024-11-26 | CVE-2017-18307 | Unspecified vulnerability in Qualcomm products Information disclosure possible while audio playback. | 5.5 |
2024-11-26 | CVE-2018-5852 | Integer Underflow (Wrap or Wraparound) vulnerability in Qualcomm products An unsigned integer underflow vulnerability in IPA driver result into a buffer over-read while reading NAT entry using debugfs command 'cat /sys/kernel/debug/ipa/ip4_nat' | 7.8 |
2024-11-26 | CVE-2016-10394 | Improper Authentication vulnerability in Qualcomm products Initial xbl_sec revision does not have all the debug policy features and critical checks. | 7.8 |
2024-11-26 | CVE-2017-11076 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Qualcomm products On some hardware revisions where VP9 decoding is hardware-accelerated, the frame size is not programmed correctly into the decoder hardware which can lead to an invalid memory access by the decoder. | 9.8 |