Bug 1894589 (CVE-2020-29371)

Summary:	CVE-2020-29371 kernel: crafted romfs filesystem leaks uninitialized memory to userspace
Product:	[Other] Security Response	Reporter:	Guilherme de Almeida Suckevicz <gsuckevi>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	acaringi, adscvr, airlied, bhu, blc, bmasney, brdeoliv, bskeggs, dhoward, dvlasenk, esammons, fhrbata, hdegoede, hkrzesin, iboverma, itamar, jarodwilson, jeremy, jforbes, jglisse, jlelli, jonathan, josef, jross, jshortt, jstancek, jwboyer, kcarcia, kernel-maint, kernel-mgr, lgoncalv, linville, masami256, mchehab, mcressma, mjg59, mlangsdo, nmurray, ptalbert, qzhao, rt-maint, rvrbovsk, 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:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-05 12:24:48 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:	1894913
Bug Blocks:	1868928

Description Guilherme de Almeida Suckevicz 2020-11-04 15:09:42 UTC

Linux Kernel could allow a local authenticated attacker to obtain sensitive information, caused by a flaw in the romfs_dev_read function in romfs_dev_read. By using a specially-crafted file, an attacker could exploit this vulnerability to obtain uninitialized memory information in userspace.

Reference:
https://bugs.chromium.org/p/project-zero/issues/detail?id=2077

Upstream patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2935e0a3cec1ffa558eea90db6279cff83aa3592

Comment 1 Petr Matousek 2020-11-05 12:25:58 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1894913]

Comment 2 Justin M. Forbes 2020-11-05 14:32:58 UTC

This was fixed for Fedora with the 5.8.4 stable kernel updates.