Bug 2267801 (CVE-2023-52516)

Summary: CVE-2023-52516 kernel: dma-debug: don't call __dma_entry_alloc_check_leak() under free_entries_lock
Product: [Other] Security Response Reporter: Zack Miele <zmiele>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sidakwo, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone: ---Keywords: Reopened, Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel 5.10.198, kernel 5.15.134, kernel 6.1.56, kernel 6.5.6, kernel 6.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-04 21:06:20 UTC 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: 2267815    

Description Zack Miele 2024-03-04 19:46:08 UTC 
In the Linux kernel, the following vulnerability has been resolved:

dma-debug: don&#39;t call __dma_entry_alloc_check_leak() under free_entries_lock

The Linux kernel CVE team has assigned CVE-2023-52516 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52516-9b4a@gregkh/T/#u
Comment 3 Alex 2024-06-09 16:50:41 UTC 
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52516 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags DEADLOCK DANGER LEAK DMAorINTERRUPT HARDWARE  ; 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.