A vulnerability in the Cisco Aironet Series Access Points (APs) software could allow an authenticated, adjacent attacker to cause an affected device to reload unexpectedly, resulting in a denial of service (DoS) condition. The vulnerability is due to a deadlock condition that may occur when an affected AP attempts to dequeue aggregated traffic that is destined to an attacker-controlled wireless client. An attacker who can successfully transition between multiple Service Set Identifiers (SSIDs) hosted on the same AP while replicating the required traffic patterns could trigger the deadlock condition. A watchdog timer that detects the condition will trigger a reload of the device, resulting in a DoS condition while the device restarts.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Aironet_access_points | Cisco | 8.2(166.0) (including) | 8.2(166.0) (including) |
| Aironet_access_points | Cisco | 8.2(167.3) (including) | 8.2(167.3) (including) |
| Aironet_access_points | Cisco | 8.3(133.0) (including) | 8.3(133.0) (including) |
| Aironet_access_points | Cisco | 8.3(141.10) (including) | 8.3(141.10) (including) |
| Aironet_access_points | Cisco | 8.5(120.0) (including) | 8.5(120.0) (including) |
| Aironet_access_points | Cisco | 8.7(1.96) (including) | 8.7(1.96) (including) |
| Aironet_access_points | Cisco | 8.7(1.99) (including) | 8.7(1.99) (including) |
| Aironet_access_points | Cisco | 8.7(1.107) (including) | 8.7(1.107) (including) |
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.