Bug 2284573 (CVE-2024-36888)

Summary: CVE-2024-36888 kernel: workqueue: Fix selection of wake_cpu in kick_pool()
Product: [Other] Security Response Reporter: Rohit Keshri <rkeshri>
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, 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, 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 6.6.31, kernel 6.8.10, kernel 6.9 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: 2284574    
Bug Blocks: 2284620    

Description Rohit Keshri 2024-06-03 13:43:15 UTC 
In the Linux kernel, the following vulnerability has been resolved:

workqueue: Fix selection of wake_cpu in kick_pool()

The Linux kernel CVE team has assigned CVE-2024-36888 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024053033-CVE-2024-36888-3543@gregkh/T
Comment 1 Rohit Keshri 2024-06-03 13:43:57 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2284574]
Comment 2 Alex 2024-06-09 17:52:20 UTC 
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-36888 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags DANGER  ; 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.