CVE-2023-52595: wifi: rt2x00: restart beacon queue when hardware reset
In the Linux kernel, the following vulnerability has been resolved:
wifi: rt2x00: restart beacon queue when hardware reset
The Linux kernel CVE team has assigned CVE-2023-52595 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024030645-CVE-2023-52595-d018@gregkh/T
Other sources
In the Linux kernel, the following vulnerability has been resolved:
wifi: rt2x00: restart beacon queue when hardware reset
When a hardware reset is triggered, all registers are reset, so all queues are forced to stop in hardware interface. However, mac80211 will not automatically stop the queue. If we don't manually stop the beacon queue, the queue will be deadlocked and unable to start again. This patch fixes the issue where Apple devices cannot connect to the AP after calling ieee80211restarthw().
— NVD
Linux Kernel is vulnerable to a denial of service, caused by an error related to the restart beacon queue when hardware reset. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause a denial of service.
— IBM
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52595?
CVE-2023-52595 has been classified with moderate severity as it pertains to a vulnerability in the Linux kernel's handling of hardware resets.
How do I fix CVE-2023-52595?
To address CVE-2023-52595, update the Linux kernel to one of the patched versions, such as 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, or newer.
Which software versions are affected by CVE-2023-52595?
CVE-2023-52595 affects several Linux kernel versions, including 5.4 up to 5.4.269, 5.10 up to 5.10.210, 5.15 up to 5.15.149, and other versions up to 6.1.77.
What components are affected by CVE-2023-52595?
The vulnerability affects the rt2x00 driver in the Linux kernel, specifically related to the beacon queue during hardware resets.
Is there a known exploit for CVE-2023-52595?
As of now, there is no publicly disclosed exploit for CVE-2023-52595, but it is advisable to apply mitigations promptly.