Bug 2281790 (CVE-2024-35860)

Summary:	CVE-2024-35860 kernel: bpf: support deferring bpf_link dealloc to after RCU grace period
Product:	[Other] Security Response	Reporter:	ybuenos
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, 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.26, kernel 6.8.5, 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:	2281791
Bug Blocks:	2281792

Description ybuenos 2024-05-20 13:47:01 UTC

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

bpf: support deferring bpf_link dealloc to after RCU grace period

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

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024051935-CVE-2024-35860-04fd@gregkh/T

Comment 1 ybuenos 2024-05-20 13:47:42 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2281791]

Comment 3 Alex 2024-06-09 17:30:31 UTC

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