This page lists publicly disclosed CVE vulnerabilities affecting qualcomm sa6145p_firmware (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2026-24091 | Memory corruption while processing fastboot commands with improperly formatted input. | [email protected] | 7.2 | 0.10% | 2026-06-01 | 2026-06-17 |
| CVE-2026-24085 | Memory Corruption when processing display command line information due to improper initialization of a variable. | [email protected] | 7.2 | 0.10% | 2026-06-01 | 2026-06-17 |
| CVE-2025-59610 | Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer. | [email protected] | 6.4 | 0.06% | 2026-06-01 | 2026-06-17 |
| CVE-2025-59606 | Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization. | [email protected] | 7.8 | 0.07% | 2026-06-01 | 2026-06-17 |
| CVE-2025-59605 | Memory Corruption when processing device identifier strings that exceed the expected maximum length. | [email protected] | 7.8 | 0.07% | 2026-06-01 | 2026-06-17 |
| CVE-2025-59604 | Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. | [email protected] | 7.8 | 0.07% | 2026-06-01 | 2026-06-17 |
| CVE-2026-24082 | Memory Corruption when copying data from a freed source while executing performance counter deselect operation. | [email protected] | 7.8 | 0.07% | 2026-05-04 | 2026-06-29 |
| CVE-2025-47404 | Memory corruption when dynamically changing the size of a previously allocated buffer while its contents are being modified. | [email protected] | 6.5 | 0.07% | 2026-05-04 | 2026-06-17 |
| CVE-2025-47389 | Memory corruption when buffer copy operation fails due to integer overflow during attestation report generation. | [email protected] | 7.8 | 0.10% | 2026-04-06 | 2026-06-17 |
| CVE-2026-21385 KEV | Memory corruption while using alignments for memory allocation. | [email protected] | 7.8 | 1.07% | 2026-03-02 | 2026-06-17 |
| CVE-2025-59600 | Memory Corruption when adding user-supplied data without checking available buffer space. | [email protected] | 7.8 | 0.07% | 2026-03-02 | 2026-06-17 |
| CVE-2025-47386 | Memory Corruption while invoking IOCTL calls when concurrent access to shared buffer occurs. | [email protected] | 7.8 | 0.07% | 2026-03-02 | 2026-06-17 |
| CVE-2025-47379 | Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocation of buffer resources. | [email protected] | 7.8 | 0.07% | 2026-03-02 | 2026-06-17 |
| CVE-2025-47376 | Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls. | [email protected] | 7.8 | 0.07% | 2026-03-02 | 2026-06-17 |
| CVE-2025-47375 | Memory corruption while handling different IOCTL calls from the user-space simultaneously. | [email protected] | 7.8 | 0.07% | 2026-03-02 | 2026-06-17 |
| CVE-2025-47373 | Memory Corruption when accessing buffers with invalid length during TA invocation. | [email protected] | 7.8 | 0.07% | 2026-03-02 | 2026-06-17 |
| CVE-2025-47366 | Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input. | [email protected] | 7.1 | 0.09% | 2026-02-02 | 2026-06-17 |
| CVE-2025-47364 | Memory corruption while calculating offset from partition start point. | [email protected] | 6.8 | 0.09% | 2026-02-02 | 2026-06-17 |
| CVE-2025-47363 | Memory corruption when calculating oversized partition sizes without proper checks. | [email protected] | 6.8 | 0.09% | 2026-02-02 | 2026-06-17 |
| CVE-2025-47369 | Information disclosure when a weak hashed value is returned to userland code in response to a IOCTL call to obtain a session ID. | [email protected] | 5.5 | 0.07% | 2026-01-07 | 2026-06-17 |