Qualcomm Fsm20055 vulnerabilities

12 vulnerabilities

Known vulnerabilities in Qualcomm Fsm20055, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

8.8CVE-2025-47392qualcomm, inc.snapdragon+148
EPSS score
0.17%
Memory corruption when decoding corrupted satellite data files with invalid signature offsets.
6.1CVE-2025-47331qualcomm, inc.snapdragon+297
EPSS score
0.08%
Information disclosure while processing a firmware event.
7.8CVE-2025-27061qualcomm, inc.snapdragon+337
EPSS score
0.10%
Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmware.
7.8CVE-2025-27042qualcomm, inc.snapdragon+337
EPSS score
0.09%
Memory corruption while processing video packets received from video firmware.
7.8CVE-2024-21475qualcomm, inc.snapdragon+229
EPSS score
0.11%
Memory corruption when the payload received from firmware is not as per the expected protocol size.
7.8CVE-2024-43057qualcomm, inc.snapdragon+151
EPSS score
0.12%
Memory corruption while processing command in Glink linux.
8.4CVE-2024-33045qualcomm, inc.snapdragon+175
EPSS score
0.12%
Memory corruption when BTFM client sends new messages over Slimbus to ADSP.
7.8CVE-2024-23368qualcomm, inc.snapdragon+341
EPSS score
0.10%
Memory corruption when allocating and accessing an entry in an SMEM partition.
7.1CVE-2026-25302qualcomm, inc.snapdragon+285
EPSS score
0.06%
Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed.
8.1CVE-2026-24079qualcomm, inc.snapdragon+137
EPSS score
0.21%
Cryptographic Issue while processing registration requests with malformed or missing authentication parameters.
6.5CVE-2026-24078qualcomm, inc.snapdragon+141
EPSS score
0.17%
Information Disclosure when IPSec negotiation fails or is not established properly during NG-eCall SIP signaling.
7.8CVE-2023-43513qualcomm, inc.snapdragon+261
EPSS score
0.11%
Memory corruption while processing the event ring, the context read pointer is untrusted to HLOS and when it is passed with arbitrary values, may point to address in the middle of ring element.