Bug 2073941 (CVE-2022-28796)

Summary:	CVE-2022-28796 kernel: a use-after-free caused by a transaction_t race condition
Product:	[Other] Security Response	Reporter:	Marian Rehak <mrehak>
Component:	vulnerability	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	acaringi, adscvr, airlied, alciregi, bdettelb, bhu, chwhite, crwood, dvlasenk, esandeen, hdegoede, hkrzesin, hpa, jarod, jarodwilson, jburrell, jfaracco, jforbes, jglisse, jlelli, joe.lawrence, jonathan, josef, jshortt, jstancek, jwboyer, jwyatt, kcarcia, kernel-maint, kernel-mgr, lgoncalv, linville, lzampier, masami256, mchehab, nmurray, ptalbert, qzhao, rvrbovsk, scweaver, steved, vkumar, walters, williams
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel 5.17.1	Doc Type:	If docs needed, set a value
Doc Text:	A use-after-free flaw was found in the Linux kernel’s journaling layer of the ext4 and OCFS2 file system functionality in the way a user can trigger a race condition during writing to the file system. 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:	2073942, 2074079, 2074080, 2074081, 2074082
Bug Blocks:	2073943

Description Marian Rehak 2022-04-11 08:12:25 UTC

jbd2_journal_wait_updates in fs/jbd2/transaction.c in the Linux kernel before 5.17.1 has a use-after-free caused by a transaction_t race condition.

Reference:

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.17.1
https://github.com/torvalds/linux/commit/cc16eecae687912238ee6efbff71ad31e2bc414e

Comment 1 Marian Rehak 2022-04-11 08:12:56 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2073942]

Comment 7 Justin M. Forbes 2022-04-13 21:29:22 UTC

The fix The patch which created this issue was in 5.17-rc3 and later kernels, and the fix was brought back into 5.17.1, so stable Fedora releases are not impacted, and the Fedora 36 beta was fixed with the 5.17.1 kernel update.