Vulnerabilities > Qualcomm > Qca6391 Firmware > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2023-06-06 | CVE-2022-40533 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Qualcomm products Transient DOS due to untrusted Pointer Dereference in core while sending USB QMI request. | 5.5 |
| 2023-05-02 | CVE-2022-33273 | Out-of-bounds Read vulnerability in Qualcomm products Information disclosure due to buffer over-read in Trusted Execution Environment while QRKS report generation. | 5.5 |
| 2023-04-13 | CVE-2022-33270 | Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in Qualcomm products Transient DOS due to time-of-check time-of-use race condition in Modem while processing RRC Reconfiguration message. | 5.9 |
| 2023-04-13 | CVE-2022-33289 | Improper Validation of Array Index vulnerability in Qualcomm products Memory corruption occurs in Modem due to improper validation of array index when malformed APDU is sent from card. | 6.8 |
| 2023-03-10 | CVE-2022-22075 | Unspecified vulnerability in Qualcomm products Information Disclosure in Graphics during GPU context switch. | 5.5 |
| 2023-01-09 | CVE-2022-25725 | Release of Invalid Pointer or Reference vulnerability in Qualcomm products Denial of service in MODEM due to improper pointer handling | 5.5 |
| 2023-01-09 | CVE-2022-33252 | Out-of-bounds Read vulnerability in Qualcomm products Information disclosure due to buffer over-read in WLAN while handling IBSS beacons frame. | 5.5 |
| 2023-01-09 | CVE-2022-33253 | Out-of-bounds Read vulnerability in Qualcomm products Transient DOS due to buffer over-read in WLAN while parsing corrupted NAN frames. | 5.5 |
| 2023-01-09 | CVE-2022-33255 | Out-of-bounds Read vulnerability in Qualcomm products Information disclosure due to buffer over-read in Bluetooth HOST while processing GetFolderItems and GetItemAttribute Cmds from peer device. | 6.5 |
| 2023-01-09 | CVE-2022-33283 | Out-of-bounds Read vulnerability in Qualcomm products Information disclosure due to buffer over-read in WLAN while WLAN frame parsing due to missing frame length check. | 6.5 |