Bug 2273146 (CVE-2024-26718)

Summary:	CVE-2024-26718 kernel: dm-crypt, dm-verity: disable tasklets
Product:	[Other] Security Response	Reporter:	Robb Gatica <rgatica>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
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.1.79, kernel 6.6.18, kernel 6.7.6, kernel 6.8	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:	2273147
Bug Blocks:	2273132

Description Robb Gatica 2024-04-03 23:21:45 UTC

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

dm-crypt, dm-verity: disable tasklets

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024040344-CVE-2024-26718-7259@gregkh/T

Comment 2 Robb Gatica 2024-04-03 23:22:26 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2273147]

Comment 4 Alex 2024-06-09 17:05:44 UTC

The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-26718 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags DANGER INIT NOMEMCHK  ; 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.