wlan AP driver vulnerabilities

In the WLAN AP driver, there is a possible out-of-bounds write due to a missing bounds check. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not required for exploitation.

In the WLAN AP driver, there is a possible memory corruption due to a heap buffer overflow. This could lead to remote (proximal/adjacent) code execution with User execution privileges needed. User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local privilege escalation if a malicious actor has already obtained System privileges. User interaction is not required for exploitation.

In the wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed and no user interaction required.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local privilege escalation if a malicious actor has already obtained System privileges. No user interaction is required for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local privilege escalation if a malicious actor has already obtained System privileges. No user interaction is required for exploitation.

In the wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. User interaction is not needed for exploitation.

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00435349; Issue ID: MSV-4051.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. User interaction is not needed for exploitation.

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00441509; Issue ID: MSV-4138.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege (when OceReducedNeighborReport is disabled). User interaction is not needed for exploitation.

In the WLAN AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege (when OceReducedNeighborReport is disabled). User interaction is not needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privileges.

In the WLAN AP driver, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.

In wlan AP driver, an out-of-bounds write due to incorrect bounds check could lead to remote (proximal/adjacent) privilege escalation without user interaction.

In wlan AP driver, an out-of-bounds write due to incorrect bounds check could lead to remote (proximal/adjacent) privilege escalation without user interaction.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00419945; Issue ID: MSV-3581.

In the WLAN AP driver, there is a possible out-of-bounds write due to an incorrect bounds check, which could lead to local escalation of privilege if an attacker already has System privilege. User interaction is not needed.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. No user interaction is needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. No user interaction is needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. No user interaction is needed for exploitation.

In the wlan AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained System privilege. No user interaction is needed for exploitation.

In the WLAN AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In the WLAN AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In the WLAN AP driver, there is a possible out-of-bounds write due to an integer overflow. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In the WLAN AP driver, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.