Bug 1672232 (CVE-2019-7309)

Summary:	CVE-2019-7309 glibc: memcmp function incorrectly returns zero
Product:	[Other] Security Response	Reporter:	Dhananjay Arunesh <darunesh>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aoliva, arjun, ashankar, codonell, darunesh, dj, fweimer, glibc-bugzilla, huzaifas, law, mfabian, mnewsome, pfrankli, rth, siddhesh, yozone
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:	2019-03-05 10:13:16 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:	1685385, 1685386, 1685387
Bug Blocks:	1672257

Description Dhananjay Arunesh 2019-02-04 10:35:33 UTC

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for
the x32 architecture can incorrectly return zero (indicating that the inputs are
equal) because the RDX most significant bit is mishandled.

References:-
https://sourceware.org/bugzilla/show_bug.cgi?id=24155
https://sourceware.org/ml/libc-alpha/2019-02/msg00041.html

Comment 3 Huzaifa S. Sidhpurwala 2019-03-05 05:40:23 UTC

Created glibc tracking bugs for this issue:

Affects: fedora-all [bug 1685385]

Comment 8 Huzaifa S. Sidhpurwala 2019-03-05 10:13:21 UTC

Statement:

This issue only affects x32 arch, which is not supported in Red Hat Enterprise Linux kernels (CONFIG_X86_X32 is not set). Therefore glibc packages shipped with Red Hat Enterprise Linux are not affected.