Bug 2268315 (CVE-2023-52595)

Summary:	CVE-2023-52595 kernel: wifi: rt2x00: restart beacon queue when hardware reset
Product:	[Other] Security Response	Reporter:	Zack Miele <zmiele>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sidakwo, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2268316
Bug Blocks:	2268346

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.