Qualcomm Lemans Au Lgit Firmware
39 CVEs affecting Qualcomm Lemans Au Lgit Firmware. Latest disclosed: 2026-08-04. Critical: 1, High: 28.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2026-25289 | Critical | 9.6 | 2026-08-04 | Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values. |
CVE-2026-24088 | High | 8.2 | 2026-06-01 | Cryptographic Issue while processing a specific partition which allows unauthorized write access to load a customized bootloader. |
CVE-2026-21366 | High | 7.8 | 2026-08-04 | Memory corruption while processing a packet with a size close to the maximum allowed value. |
CVE-2025-59606 | High | 7.8 | 2026-06-01 | Memory Corruption when writing to invalid memory locations occurs due to heap memory exhaustion during secure data initialization. |
CVE-2025-59604 | High | 7.8 | 2026-06-01 | Memory Corruption when running a memory copy operation due to invalid writes caused by a null pointer. |
CVE-2026-24082 | High | 7.8 | 2026-05-04 | Memory Corruption when copying data from a freed source while executing performance counter deselect operation. |
CVE-2025-47391 | High | 7.8 | 2026-04-06 | Memory corruption while processing a frame request from user. |
CVE-2025-47389 | High | 7.8 | 2026-04-06 | Memory corruption when buffer copy operation fails due to integer overflow during attestation report generation. |
CVE-2026-21385 | High | 7.8 | 2026-03-02 | Memory corruption while using alignments for memory allocation. |
CVE-2025-59600 | High | 7.8 | 2026-03-02 | Memory Corruption when adding user-supplied data without checking available buffer space. |
CVE-2025-47386 | High | 7.8 | 2026-03-02 | Memory Corruption while invoking IOCTL calls when concurrent access to shared buffer occurs. |
CVE-2025-47385 | High | 7.8 | 2026-03-02 | Memory Corruption when accessing trusted execution environment without proper privilege check. |
CVE-2025-47381 | High | 7.8 | 2026-03-02 | Memory Corruption while processing IOCTL calls when concurrent access to shared buffer occurs. |
CVE-2025-47379 | High | 7.8 | 2026-03-02 | Memory Corruption when concurrent access to shared buffer occurs due to improper synchronization between assignment and deallocation of buffer resources. |
CVE-2025-47377 | High | 7.8 | 2026-03-02 | Memory Corruption when accessing a buffer after it has been freed while processing IOCTL calls. |
CVE-2025-47376 | High | 7.8 | 2026-03-02 | Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls. |
CVE-2025-47375 | High | 7.8 | 2026-03-02 | Memory corruption while handling different IOCTL calls from the user-space simultaneously. |
CVE-2025-47373 | High | 7.8 | 2026-03-02 | Memory Corruption when accessing buffers with invalid length during TA invocation. |
CVE-2025-47398 | High | 7.8 | 2026-02-02 | Memory Corruption while deallocating graphics processing unit memory buffers due to improper handling of memory pointers. |
CVE-2025-47397 | High | 7.8 | 2026-02-02 | Memory Corruption when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors. |