Bug 2274614 (CVE-2021-47195)

Summary:	CVE-2021-47195 kernel: spi: fix use-after-free of the add_lock mutex
Product:	[Other] Security Response	Reporter:	Marco Benatto <mbenatto>
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, 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.15.5, kernel 5.16	Doc Type:	If docs needed, set a value
Doc Text:	A use-after-free of the add_lock mutex was found in drivers/spi/spi.c.in the Linux kernel.	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:	2274637

Description Marco Benatto 2024-04-11 21:05:18 UTC

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

spi: fix use-after-free of the add_lock mutex

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024041035-CVE-2021-47195-38e8@gregkh/T

Comment 3 Alex 2024-06-09 15:27:57 UTC

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