Bug 1647972

Summary:	CVE-2018-14660 glusterfs: Repeat use of "GF_META_LOCK_KEY" xattr allows for memory exhaustion [fedora-all]
Product:	[Community] GlusterFS	Reporter:	Susant Kumar Palai <spalai>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1	CC:	anoopcs, atumball, bugs, extras-qa, humble.devassy, jonathansteffan, kkeithle, matthias, ndevos, ramkrsna, sisharma, srangana
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.6	Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:	1644758	Environment:
Last Closed:	2018-11-29 15:27:59 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:	1644582, 1644758
Bug Blocks:	1647962

Description Susant Kumar Palai 2018-11-08 16:22:57 UTC

+++ This bug was initially created as a clone of Bug #1644758 +++

+++ This bug was initially created as a clone of Bug #1644582 +++


This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

--- Additional comment from Worker Ant on 2018-11-06 10:40:29 MVT ---

REVIEW: https://review.gluster.org/21531 (lock: Do not allow meta-lock count to be more than one) posted (#4) for review on master by Amar Tumballi

Comment 1 Worker Ant 2018-11-08 16:39:41 UTC

REVIEW: https://review.gluster.org/21603 (lock: Do not allow meta-lock count to be more than one) posted (#1) for review on release-4.1 by Susant Palai

Comment 2 Worker Ant 2018-11-08 16:40:56 UTC

REVIEW: https://review.gluster.org/21604 (features/locks:Use pthread_mutex_unlock() instead of pthread_mutex_lock()) posted (#1) for review on release-4.1 by Susant Palai

Comment 3 Worker Ant 2018-11-09 14:03:50 UTC

REVIEW: https://review.gluster.org/21603 (lock: Do not allow meta-lock count to be more than one) posted (#1) for review on release-4.1 by Susant Palai

Comment 4 Worker Ant 2018-11-09 14:04:19 UTC

REVIEW: https://review.gluster.org/21604 (features/locks:Use pthread_mutex_unlock() instead of pthread_mutex_lock()) posted (#1) for review on release-4.1 by Susant Palai

Comment 5 Shyamsundar 2018-11-29 15:27:59 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.1.6, please open a new bug report.

glusterfs-4.1.6 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-November/000116.html
[2] https://www.gluster.org/pipermail/gluster-users/