Bug 2282590 (CVE-2021-47227)

Summary:	CVE-2021-47227 kernel: x86/fpu: Prevent state corruption in __fpu__restore_sig()
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.10.46, kernel 5.12.13, kernel 5.13	Doc Type:	If docs needed, set a value
Doc Text:	A vulnerability was found in the Linux kernel's x86/fpu, within the __fpu__restore_sig() function. When user data is copied into the kernel buffer without proper validation, it can lead to corruption of the kernel's state, resulting in a system crash when using the FPU.	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:	2282975

Description ybuenos 2024-05-22 15:40:14 UTC

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

x86/fpu: Prevent state corruption in __fpu__restore_sig()

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052137-CVE-2021-47227-8364@gregkh/T

Comment 3 Alex 2024-06-09 15:32:17 UTC

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