Bug 2282525 (CVE-2021-47274)

Summary:	CVE-2021-47274 kernel: tracing: Correct the length check which causes memory corruption
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, 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.9.273, 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 tracing system, where improper length checks in the code can lead to memory corruption. This issue can cause kernel crash by allowing out-of-bounds writes when handling trace data, potentially resulting in severe system instability and data loss.	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:	2282973

Description ybuenos 2024-05-22 14:00:23 UTC

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

tracing: Correct the length check which causes memory corruption

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052151-CVE-2021-47274-3867@gregkh/T

Comment 2 Alex 2024-06-09 16:07:08 UTC

The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-47274 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is an approximation based on flags WRITE OOB DANGER TRACE IMPROVEONLY  ; these flags parsed automatically based on patch 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.