Bug 2275719 (CVE-2024-26866)

Summary:	CVE-2024-26866 kernel: spi: lpspi: Avoid potential use-after-free in probe()
Product:	[Other] Security Response	Reporter:	Robb Gatica <rgatica>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	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.6.23, kernel 6.7.11, kernel 6.8.2, kernel 6.9-rc1	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:	2275720
Bug Blocks:	2275739

Description Robb Gatica 2024-04-17 18:40:39 UTC

In the Linux kernel, the following vulnerability has been resolved:

spi: lpspi: Avoid potential use-after-free in probe()

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024041737-CVE-2024-26866-1e98@gregkh/T

Comment 1 Robb Gatica 2024-04-17 18:41:13 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2275720]

Comment 4 Alex 2024-06-09 15:25:46 UTC

The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-26866 is: CHECK	Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags NULLPTR UAF  ; 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.