Bug 2150845 (CVE-2022-20153)

Summary:	CVE-2022-20153 kernel: possible use-after-free due to improper locking in rcu_cblist_dequeue of rcu_segcblist.c
Product:	[Other] Security Response	Reporter:	Alex <allarkin>
Component:	vulnerability	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	acaringi, adscvr, airlied, alciregi, bhu, chwhite, crwood, ddepaula, debarbos, dvlasenk, ezulian, hkrzesin, hpa, jarod, jarodwilson, jfaracco, jferlan, jforbes, jglisse, jlelli, joe.lawrence, josef, jshortt, jstancek, jwboyer, jwyatt, kcarcia, kernel-maint, kernel-mgr, lgoncalv, linville, lzampier, masami256, mchehab, nmurray, ptalbert, qzhao, rvrbovsk, scweaver, steved, walters, williams
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 use-after-free flaw was found in the Linux kernel’s io_uring (in fs/io_uring.c) when improper locking happens. This flaw allows a local user to crash or potentially escalate their privileges on the system.	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:	2150846, 2150847, 2150848
Bug Blocks:	2099268

Description Alex 2022-12-05 12:06:29 UTC

In rcu_cblist_dequeue of rcu_segcblist.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with System execution privileges needed. User interaction is not needed for exploitation.

References:
https://github.com/torvalds/linux/commit/f70865db5ff35f5ed0c7e9ef63e7cca3d4947f04
https://bugzilla.suse.com/show_bug.cgi?id=1200609

Comment 1 Alex 2022-12-05 12:06:58 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2150846]

Comment 4 Justin M. Forbes 2022-12-08 15:31:06 UTC

This was fixed for Fedora with the 5.13 stable kernel rebases