Bug 2282517 (CVE-2021-47280)

Summary:	CVE-2021-47280 kernel: drm: Fix use-after-free read in drm_getunique()
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, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mbenatto, mleitner, mmilgram, mstowell, ndegraef, 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 4.14.237, kernel 4.19.195, kernel 5.4.126, kernel 5.10.44, kernel 5.12.11, kernel 5.13	Doc Type:	If docs needed, set a value
Doc Text:	A vulnerability was found in the Linux kernel's DRM, where the drm_getunique() function can read a pointer after it has been freed. This occurs because the function retrieves a pointer without properly locking the device's master mutex, leading to a potential crash if another process modifies the pointer first.	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:	2282972

Description ybuenos 2024-05-22 13:48:37 UTC

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

drm: Fix use-after-free read in drm_getunique()

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052153-CVE-2021-47280-4344@gregkh/T

Comment 5 Alex 2024-06-09 15:42:14 UTC

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