Bug 2283397 (CVE-2021-47552)

Summary:	CVE-2021-47552 kernel: blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and disk_release()
Product:	[Other] Security Response	Reporter:	ybuenos
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, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jfaracco, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, ldoskova, lgoncalv, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, scweaver, sidakwo, sukulkar, tglozar, trathi, vkumar, wcosta, williams, wmealing, ycote, ykopkova
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel 5.15.6, kernel 5.16	Doc Type:	If docs needed, set a value
Doc Text:	A vulnerability was found in the Linux kernel's block blk-mq when dispatch work was handled during queue cleanup. This issue occurs when dispatch work is not properly canceled in both the blk_cleanup_queue() and disk_release() functions, which can lead to a NULL pointer dereference if the associated SCSI device is freed before dispatch work is completed, resulting in kernel crashes and disruption in block device operations.	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:
Bug Blocks:	2283496

Description ybuenos 2024-05-27 09:48:29 UTC

In the Linux kernel, the following vulnerability has been resolved:

blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and disk_release()

The Linux kernel CVE team has assigned CVE-2021-47552 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052442-CVE-2021-47552-99f3@gregkh/T

Comment 2 Alex 2024-06-09 15:45:53 UTC

The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-47552 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags DANGER NULLPTR DISK INIT  ; 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.