Bug 2266286 (CVE-2024-26606)

Summary:	CVE-2024-26606 kernel: signal epoll threads of self-work
Product:	[Other] Security Response	Reporter:	Rohit Keshri <rkeshri>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	CLOSED NOTABUG	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, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	A flaw was found in the Linux kernel. This issue is in the binder subsystem.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-03-12 17:54:41 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:	2266288
Bug Blocks:	2266287

Description Rohit Keshri 2024-02-27 12:50:12 UTC

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

binder: signal epoll threads of self-work

In (e)poll mode, threads often depend on I/O events to determine when
data is ready for consumption. Within binder, a thread may initiate a
command via BINDER_WRITE_READ without a read buffer and then make use
of epoll_wait() or similar to consume any responses afterwards.

It is then crucial that epoll threads are signaled via wakeup when they
queue their own work. Otherwise, they risk waiting indefinitely for an
event leaving their work unhandled. What is worse, subsequent commands
won't trigger a wakeup either as the thread has pending work.

https://git.kernel.org/stable/c/42beab162dcee1e691ee4934292d51581c29df61
https://git.kernel.org/stable/c/82722b453dc2f967b172603e389ee7dc1b3137cc
https://git.kernel.org/stable/c/90e09c016d72b91e76de25f71c7b93d94cc3c769
https://git.kernel.org/stable/c/93b372c39c40cbf179e56621e6bc48240943af69
https://git.kernel.org/stable/c/97830f3c3088638ff90b20dfba2eb4d487bf14d7
https://git.kernel.org/stable/c/a423042052ec2bdbf1e552e621e6a768922363cc
https://git.kernel.org/stable/c/a7ae586f6f6024f490b8546c8c84670f96bb9b68
https://git.kernel.org/stable/c/dd64bb8329ce0ea27bc557e4160c2688835402ac

Comment 1 Rohit Keshri 2024-02-27 13:01:36 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2266288]

Comment 8 Alex 2024-06-09 13:12:47 UTC

The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-26606 is: 	SKIP	No affected files built, so skip this CVE	NO			-	-	unknown (where first YES/NO value means if related sources built).