Bug 2282879 (CVE-2021-47435)

Summary: CVE-2021-47435 kernel: dm: fix mempool NULL pointer race when completing IO
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, bmarzins, 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.313, kernel 4.14.278, kernel 4.19.242, kernel 5.4.193, kernel 5.10.113, kernel 5.14.14, kernel 5.15 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: 2316346    
Bug Blocks: 2283369    

Description ybuenos 2024-05-23 09:09:36 UTC 
In the Linux kernel, the following vulnerability has been resolved:

dm: fix mempool NULL pointer race when completing IO

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024052238-CVE-2021-47435-65c6@gregkh/T
Comment 1 Alex 2024-06-09 16:08:46 UTC 
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-47435 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is an approximation based on flags DANGER NULLPTR RACE  ; 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.