Search
Search Results (916 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-24079 | 1 Qualcomm | 1 Snapdragon | 2026-08-07 | 8.1 High |
| Cryptographic Issue while processing registration requests with malformed or missing authentication parameters. | ||||
| CVE-2026-24076 | 1 Qualcomm | 1 Snapdragon | 2026-08-06 | 6.7 Medium |
| Memory Corruption when processing registry values with incorrect types using a direct query method. | ||||
| CVE-2026-25292 | 1 Qualcomm | 1 Snapdragon | 2026-08-05 | 7.6 High |
| Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration. | ||||
| CVE-2026-24080 | 1 Qualcomm | 1 Snapdragon | 2026-08-05 | 7.8 High |
| Memory Corruption when handling malformed request parameters in the fingerprint TA. | ||||
| CVE-2026-25288 | 1 Qualcomm | 1 Snapdragon | 2026-08-05 | 7.4 High |
| Transient DOS when processing a short target wake time channel usage response frame with insufficient packet size. | ||||
| CVE-2026-25289 | 1 Qualcomm | 1 Snapdragon | 2026-08-05 | 9.6 Critical |
| Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values. | ||||
| CVE-2026-24078 | 1 Qualcomm | 1 Snapdragon | 2026-08-04 | 6.5 Medium |
| Information Disclosure when IPSec negotiation fails or is not established properly during NG-eCall SIP signaling. | ||||
| CVE-2026-24083 | 1 Qualcomm | 1 Snapdragon | 2026-08-04 | 7.8 High |
| Memory Corruption while processing IOCTL device driver requests with invalid arguments. | ||||
| CVE-2026-24084 | 1 Qualcomm | 1 Snapdragon | 2026-08-04 | 7.5 High |
| Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities. | ||||
| CVE-2026-21366 | 1 Qualcomm | 1 Snapdragon | 2026-08-04 | 7.8 High |
| Memory corruption while processing a packet with a size close to the maximum allowed value. | ||||
| CVE-2026-21369 | 1 Qualcomm | 1 Snapdragon | 2026-07-09 | 5.3 Medium |
| Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification. | ||||
| CVE-2026-21384 | 1 Qualcomm | 1 Snapdragon | 2026-07-08 | 5.3 Medium |
| Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits. | ||||
| CVE-2025-59615 | 1 Qualcomm | 1 Snapdragon | 2026-07-08 | 6.6 Medium |
| Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization. | ||||
| CVE-2025-59616 | 1 Qualcomm | 1 Snapdragon | 2026-07-08 | 6.6 Medium |
| Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input due to accessing already freed memory. | ||||
| CVE-2025-59617 | 1 Qualcomm | 1 Snapdragon | 2026-07-07 | 6.6 Medium |
| Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input. | ||||
| CVE-2026-21368 | 1 Qualcomm | 1 Snapdragon | 2026-07-07 | 5.3 Medium |
| Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks. | ||||
| CVE-2026-21370 | 1 Qualcomm | 1 Snapdragon | 2026-07-07 | 5.3 Medium |
| Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values. | ||||
| CVE-2026-25271 | 1 Qualcomm | 1 Snapdragon | 2026-07-07 | 7.8 High |
| Memory Corruption when processing asynchronous input parameters due to improper handling of modified values between check and use. | ||||
| CVE-2026-21379 | 1 Qualcomm | 1 Snapdragon | 2026-07-06 | 7.8 High |
| Memory Corruption when allocating memory with sizes that exceed the maximum allowed value. | ||||
| CVE-2025-59610 | 1 Qualcomm | 473 5g Fixed Wireless Access Platform, 5g Fixed Wireless Access Platform Firmware, C-v2x 9150 and 470 more | 2026-06-05 | 6.4 Medium |
| Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer. | ||||