Srv1l Firmware
by Qualcomm
CVEs (163)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2024-33050 | Hig | 0.49 | 7.5 | 0.00 | Sep 2, 2024 | Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper. | ||
| CVE-2024-33048 | Hig | 0.49 | 7.5 | 0.00 | Sep 2, 2024 | Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame. | ||
| CVE-2024-23364 | Hig | 0.49 | 7.5 | 0.00 | Sep 2, 2024 | Transient DOS when processing the non-transmitted BSSID profile sub-elements present within the MBSSID Information Element (IE) of a beacon frame that is received from over-the-air (OTA). | ||
| CVE-2024-33026 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing probe response and assoc response frame when received frame length is less than max size of timestamp. | ||
| CVE-2024-33025 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing the BSS parameter change count or MLD capabilities fields of the ML IE. | ||
| CVE-2024-33024 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing the ML IE when a beacon with length field inside the common info of ML IE greater than the ML IE length. | ||
| CVE-2024-33020 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while processing TID-to-link mapping IE elements. | ||
| CVE-2024-33019 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing the received TID-to-link mapping action frame. | ||
| CVE-2024-33018 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing the received TID-to-link mapping element of the TID-to-link mapping action frame. | ||
| CVE-2024-33015 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing SCAN RNR IE when bytes received from AP is such that the size of the last param of IE is less than neighbor report. | ||
| CVE-2024-33014 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing ESP IE from beacon/probe response frame. | ||
| CVE-2024-33013 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS when driver accesses the ML IE memory and offset value is incremented beyond ML IE length. | ||
| CVE-2024-33012 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing the multiple MBSSID IEs from the beacon, when the tag length is non-zero value but with end of beacon. | ||
| CVE-2024-33011 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing the MBSSID IE from the beacons, when the MBSSID IE length is zero. | ||
| CVE-2024-33010 | Hig | 0.49 | 7.5 | 0.00 | Aug 5, 2024 | Transient DOS while parsing fragments of MBSSID IE from beacon frame. | ||
| CVE-2025-21425 | Hig | 0.47 | 7.3 | 0.00 | Apr 7, 2025 | Memory corruption may occur due top improper access control in HAB process. | ||
| CVE-2024-21469 | Hig | 0.47 | 7.3 | 0.00 | Jul 1, 2024 | Memory corruption when an invoke call and a TEE call are bound for the same trusted application. | ||
| CVE-2025-47366 | Hig | 0.46 | 7.1 | 0.00 | Feb 2, 2026 | Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input. | ||
| CVE-2025-21482 | Hig | 0.46 | 7.1 | 0.00 | Sep 24, 2025 | Cryptographic issue while performing RSA PKCS padding decoding. | ||
| CVE-2025-21422 | Hig | 0.46 | 7.1 | 0.00 | Jul 8, 2025 | Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses. |
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame.
- risk 0.49cvss 7.5epss 0.00
Transient DOS when processing the non-transmitted BSSID profile sub-elements present within the MBSSID Information Element (IE) of a beacon frame that is received from over-the-air (OTA).
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing probe response and assoc response frame when received frame length is less than max size of timestamp.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing the BSS parameter change count or MLD capabilities fields of the ML IE.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing the ML IE when a beacon with length field inside the common info of ML IE greater than the ML IE length.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while processing TID-to-link mapping IE elements.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing the received TID-to-link mapping action frame.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing the received TID-to-link mapping element of the TID-to-link mapping action frame.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing SCAN RNR IE when bytes received from AP is such that the size of the last param of IE is less than neighbor report.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing ESP IE from beacon/probe response frame.
- risk 0.49cvss 7.5epss 0.00
Transient DOS when driver accesses the ML IE memory and offset value is incremented beyond ML IE length.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing the multiple MBSSID IEs from the beacon, when the tag length is non-zero value but with end of beacon.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing the MBSSID IE from the beacons, when the MBSSID IE length is zero.
- risk 0.49cvss 7.5epss 0.00
Transient DOS while parsing fragments of MBSSID IE from beacon frame.
- risk 0.47cvss 7.3epss 0.00
Memory corruption may occur due top improper access control in HAB process.
- risk 0.47cvss 7.3epss 0.00
Memory corruption when an invoke call and a TEE call are bound for the same trusted application.
- risk 0.46cvss 7.1epss 0.00
Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input.
- risk 0.46cvss 7.1epss 0.00
Cryptographic issue while performing RSA PKCS padding decoding.
- risk 0.46cvss 7.1epss 0.00
Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses.
Page 7 of 9