qca6426 firmware vulnerabilities and fixes

Recent CVEs affecting qca6426 firmware, with upgrade or downgrade steps. 21 tracked.

Also searched as: qca6426firmware.

qca6426 firmware has 21 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2025-09-24. Highest priority: CVE-2023-28581 (score 50/100).

• CVE-2025-27071 HIGH 7.3 MITIGATE MITIGATE Memory corruption while processing specific files in Powerline Communication Firmware.
• CVE-2025-27037 HIGH 7.8 MITIGATE MITIGATE Memory corruption while processing config_dev IOCTL when camera kernel driver drops its reference to CPU buffe
• CVE-2025-21474 HIGH 7.8 MITIGATE MITIGATE Memory corruption while processing commands from A2dp sink command queue.
• CVE-2025-21455 HIGH 7.8 MITIGATE MITIGATE Memory corruption while submitting blob data to kernel space though IOCTL.
• CVE-2024-53016 MEDIUM 6.6 MITIGATE MITIGATE Memory corruption while processing I2C settings in Camera driver.
• CVE-2024-45570 MEDIUM 6.6 MITIGATE MITIGATE Memory corruption may occur during IO configuration processing when the IO port count is invalid.
• CVE-2024-45566 HIGH 7.8 MITIGATE MITIGATE Memory corruption during concurrent buffer access due to modification of the reference count.
• CVE-2024-45544 MEDIUM 6.6 MITIGATE MITIGATE Memory corruption while processing IOCTL calls to add route entry in the HW.
• CVE-2024-43067 HIGH 7.8 MITIGATE MITIGATE Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is expos
• CVE-2024-33040 MEDIUM 6.7 MITIGATE MITIGATE Memory corruption while invoking redundant release command to release one buffer from user space as race condi
• CVE-2023-43527 MEDIUM 6.8 MITIGATE MITIGATE Information disclosure while parsing dts header atom in Video.
• CVE-2023-28581 CRITICAL 9.8 MITIGATE MITIGATE Memory corruption in WLAN Firmware while parsing receieved GTK Keys in GTK KDE.
• CVE-2023-28577 MEDIUM 6.7 MITIGATE MITIGATE In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used
• CVE-2023-28576 MEDIUM 6.4 MITIGATE MITIGATE The buffer obtained from kernel APIs such as cam_mem_get_cpu_buf() may be readable/writable in userspace after
• CVE-2023-21667 MEDIUM 6.5 MITIGATE MITIGATE Transient DOS in Bluetooth HOST while passing descriptor to validate the blacklisted BT keyboard.
• CVE-2023-21647 MEDIUM 6.5 MITIGATE MITIGATE Information disclosure in Bluetooth when an GATT packet is received due to improper input validation.
• CVE-2023-21644 MEDIUM 6.7 MITIGATE MITIGATE Memory corruption in RIL due to Integer Overflow while triggering qcril_uim_request_apdu request.
• CVE-2023-21636 MEDIUM 6.7 MITIGATE MITIGATE Memory Corruption due to improper validation of array index in Linux while updating adn record.
• CVE-2023-21627 MEDIUM 6.7 MITIGATE MITIGATE Memory corruption in Trusted Execution Environment while calling service API with invalid address.
• CVE-2022-40524 MEDIUM 6.7 MITIGATE MITIGATE Memory corruption due to buffer over-read in Modem while processing SetNativeHandle RTP service.
• CVE-2022-33220 MEDIUM 5.1 MITIGATE MITIGATE Information disclosure in Automotive multimedia due to buffer over-read.

FAQ

How do I fix qca6426 firmware vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is qca6426 firmware being exploited right now?

None of the tracked qca6426 firmware CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which qca6426 firmware CVE should I patch first?

CVE-2023-28581 currently ranks highest (50/100): Memory corruption in WLAN Firmware while parsing receieved GTK Keys in GTK KDE..

RSS feed for qca6426 firmware · ← Back to latest CVEs