Bug 2283466 (CVE-2021-47565)

Summary: CVE-2021-47565 kernel: scsi: mpt3sas: Fix kernel panic during drive powercycle test
Product: [Other] Security Response Reporter: ybuenos
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, emilne, 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, trathi, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel 4.4.294, kernel 4.9.292, kernel 4.14.257, kernel 4.19.219, kernel 5.4.163, kernel 5.10.83, kernel 5.15.6, kernel 5.16 Doc Type: If docs needed, set a value
Doc Text:
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: 2283496    

Description ybuenos 2024-05-27 11:20:31 UTC 
In the Linux kernel, the following vulnerability has been resolved:

scsi: mpt3sas: Fix kernel panic during drive powercycle test

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052452-CVE-2021-47565-5f60@gregkh/T
Comment 2 Alex 2024-06-09 15:44:47 UTC 
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-47565 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags DANGER SIMPLEFIX  ; 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.