Search CVEs

Transient DOS can occur when the driver parses the per STA profile IE and tries to access the EXTN element ID without checking the IE length.

Transient DOS when driver accesses the ML IE memory and offset value is incremented beyond ML IE length.

Transient DOS may occur while parsing extended IE in beacon.

Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests.

Transient DOS while processing TID-to-link mapping IE elements.

Transient DOS while parsing per STA profile in ML IE.

Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper.

Transient DOS may occur while parsing EHT operation IE or EHT capability IE.

Transient DOS while parsing the received TID-to-link mapping element of the TID-to-link mapping action frame.

Transient DOS while parsing BTM ML IE when per STA profile is not included.

Transient DOS while parsing noninheritance IE of Extension element when length of IE is 2 of beacon frame.

Transient DOS may occur while processing malformed length field in SSID IEs.

Transient DOS while parsing the received TID-to-link mapping action frame.

Transient DOS while handling beacon frames with invalid IE header length.

Transient DOS while parsing the multi-link element Control field when common information length check is missing before updating the location.

Transient DOS while parsing the MBSSID IE from the beacons, when the MBSSID IE length is zero.

Transient DOS while parsing the MBSSID IE from the beacons when IE length is 0.

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).

Transient DOS while processing TIM IE from beacon frame as there is no check for IE length.

Transient DOS can occur while processing UCI command.