In DA, there is a possible out of bounds write due to a missing bounds check

In DA, there is a possible out of bounds write due to a missing bounds check

In da, there is a possible out of bounds write due to a missing bounds check

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check

In gnss service, there is a possible out of bounds write due to an incorrect bounds check

In gnss service, there is a possible out of bounds write due to an incorrect bounds check

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check

In preloader, there is a possible escalation of privilege due to an insecure default value

In gnss service, there is a possible out of bounds write due to improper input validation

In preloader, there is a possible escalation of privilege due to an insecure default value

In flashc, there is a possible out of bounds write due to lack of valudation

In lk, there is a possible escalation of privilege due to a missing bounds check

In da, there is a possible out of bounds write due to a missing bounds check

In aee, there is a possible escalation of privilege due to a missing permission check

In gnss service, there is a possible out of bounds write due to improper input validation

In wlan driver, there is a possible out of bounds write due to improper input validation

In gps, there is a possible out of bounds write due to a missing bounds check

In gps, there is a possible out of bounds write due to a missing bounds check

In gps, there is a possible out of bounds write due to a missing bounds check

In gps, there is a possible out of bounds write due to a missing bounds check

In gps, there is a possible out of bounds write due to a missing bounds check

In nvram, there is a possible out of bounds write due to a missing bounds check

In display, there is a possible out of bounds write due to a missing bounds check

In preloader, there is a possible out of bounds write due to a missing bounds check

In preloader, there is a possible out of bounds write due to a missing bounds check

In preloader, there is a possible out of bounds write due to a missing bounds check

In preloader, there is a possible out of bounds write due to a missing bounds check

In V6 DA, there is a possible out of bounds write due to a missing bounds check

In V6 DA, there is a possible out of bounds write due to a missing bounds check

In V6 DA, there is a possible out of bounds write due to a missing bounds check

In V6 DA, there is a possible out of bounds write due to a missing bounds check

In wlan service, there is a possible out of bounds write due to improper input validation

In wlan driver, there is a possible out of bounds write due to improper input validation

In gnss, there is a possible escalation of privilege due to a missing bounds check

odhcpd: pre-auth remote DoS via size_t underflow in dhcpv6_ia_handle_IAs (stack BOF, canary-terminated)

OpenWrt: EAD Integer Underflow → Pre-Auth Denial of Service

In wlan AP/STA firmware, there is a possible system becoming irresponsive due to an uncaught exception

In Bluetooth FW, there is a possible system crash due to an uncaught exception

In Bluetooth FW, there is a possible system crash due to an uncaught exception

In wlan STA driver, there is a possible out of bounds read due to an incorrect bounds check

In Bluetooth Stack SW, there is a possible information disclosure due to a missing permission check

In Bluetooth firmware, there is a possible firmware asssert due to improper handling of exceptional conditions

In OpenWrt 19.07.x before 19.07.7, when IPv6 is used, a routing loop can occur that generates excessive network traffic between an affected device and its upstream ISP's router

In da, there is a possible out of bounds read due to a missing bounds check

In da, there is a possible out of bounds read due to a missing bounds check

There is missing input validation of host names displayed in OpenWrt before 19.07.8

cgi_handle_request in uhttpd in OpenWrt through 18.06.1 and LEDE through 17.01 has unauthenticated reflected XSS via the URI, as demonstrated by a cgi-bin/?[XSS] URI