Bug 2282453 (CVE-2021-47318)

Summary:	CVE-2021-47318 kernel: arch_topology: Avoid use-after-free for scale_freq_data
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, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, scweaver, sidakwo, sukulkar, tglozar, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel 5.13.4, kernel 5.14	Doc Type:	If docs needed, set a value
Doc Text:	A vulnerability was found in the topology_scale_freq_tick() function in the Linux kernel's architecture topology management. This function may use a pointer to struct scale_freq_data that has already been cleared, leading to a use-after-free condition. This can happen because there is no mechanism to ensure the cleared data is not accessed again.	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:	2282500

Description ybuenos 2024-05-22 12:06:46 UTC

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

arch_topology: Avoid use-after-free for scale_freq_data

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052131-CVE-2021-47318-fffb@gregkh/T

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

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