Bug 2268315 (CVE-2023-52595) - CVE-2023-52595 kernel: wifi: rt2x00: restart beacon queue when hardware reset
Summary: CVE-2023-52595 kernel: wifi: rt2x00: restart beacon queue when hardware reset
Keywords:
Status: NEW
Alias: CVE-2023-52595
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2268316
Blocks: 2268346
TreeView+ depends on / blocked
 
Reported: 2024-03-06 22:18 UTC by Zack Miele
Modified: 2024-09-18 18:56 UTC (History)
50 users (show)

Fixed In Version: kernel 5.4.269, kernel 5.10.210, kernel 5.15.149, kernel 6.1.77, kernel 6.6.16, kernel 6.7.4, kernel 6.8-rc1
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the Linux kernel. When a hardware reset is triggered, all registers are reset, so all queues are forced to stop in the hardware interface. However, mac80211 will not automatically stop the queue. If the beacon queue is not manually stopped, it will be deadlocked and unable to restart.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2024:3622 0 None None None 2024-06-05 09:02:13 UTC
Red Hat Product Errata RHBA-2024:3773 0 None None None 2024-06-10 15:11:18 UTC
Red Hat Product Errata RHBA-2024:3990 0 None None None 2024-06-20 01:13:56 UTC
Red Hat Product Errata RHSA-2024:3618 0 None None None 2024-06-05 00:31:22 UTC
Red Hat Product Errata RHSA-2024:3627 0 None None None 2024-06-05 10:04:29 UTC

Description Zack Miele 2024-03-06 22:18:29 UTC 
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
Comment 1 Zack Miele 2024-03-06 22:19:04 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2268316]
Comment 2 Justin M. Forbes 2024-03-07 23:48:22 UTC 
This was fixed for Fedora with the 6.7.4 stable kernel updates.
Comment 4 errata-xmlrpc 2024-06-05 00:31:19 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:3618 https://access.redhat.com/errata/RHSA-2024:3618
Comment 5 errata-xmlrpc 2024-06-05 10:04:25 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2024:3627 https://access.redhat.com/errata/RHSA-2024:3627
Comment 7 Alex 2024-06-09 15:18:36 UTC 
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52595 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags REMOTE DEADLOCK SIMPLEFIX  ; these flags parsed automatically based on patche data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.
Note You need to log in before you can comment on or make changes to this bug.