Bug 2278208 (CVE-2024-26945)

Summary: CVE-2024-26945 kernel: crypto: iaa - Fix nr_cpus < nr_iaa case
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, 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: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel 6.8.3, kernel 6.9-rc2 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: 2278209    
Bug Blocks: 2278552    

Description Zack Miele 2024-05-01 16:56:39 UTC
In the Linux kernel, the following vulnerability has been resolved:

crypto: iaa - Fix nr_cpus &lt; nr_iaa case

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024050126-CVE-2024-26945-bf47@gregkh/T

Comment 2 Zack Miele 2024-05-01 16:57:19 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2278209]

Comment 3 Alex 2024-06-09 16:43:30 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-26945 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags SIMPLEFIX  ; 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.