Bug 1805925

Summary: CVE-2020-8991 lvm2: memory leak in vg_lookup in daemons/lvmetad/lvmetad-core.c [fedora-all]
Product: [Fedora] Fedora Reporter: Guilherme de Almeida Suckevicz <gsuckevi>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 31CC: agk, anprice, bmarzins, bmr, cfeist, heinzm, jbrassow, jonathan, kzak, lvm-team, mcsontos, msnitzer, prajnoha, prockai, zkabelac
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-27 18:04:49 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:    
Bug Blocks: 1805922    

Description Guilherme de Almeida Suckevicz 2020-02-21 17:32:32 UTC
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.

Comment 1 Guilherme de Almeida Suckevicz 2020-02-21 17:32:35 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1805922,1805925

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 3 Marian Csontos 2020-02-24 09:56:46 UTC
I wonder why is this using the old lvm2 package, while newer ones which dropped lvmetad are available in Fedora 31?

Comment 5 Guilherme de Almeida Suckevicz 2020-02-26 20:06:37 UTC
(In reply to Marian Csontos from comment #3)
> I wonder why is this using the old lvm2 package, while newer ones which
> dropped lvmetad are available in Fedora 31?

What do you mean by old lvm2 package?
If Fedora uses an already fixed version you can close this as NOTABUG.

Comment 7 Jonathan Earl Brassow 2020-02-27 18:04:49 UTC
(In reply to Guilherme de Almeida Suckevicz from comment #5)
> (In reply to Marian Csontos from comment #3)
> > I wonder why is this using the old lvm2 package, while newer ones which
> > dropped lvmetad are available in Fedora 31?
> 
> What do you mean by old lvm2 package?
> If Fedora uses an already fixed version you can close this as NOTABUG.

lvmetad is not available in Fedora 31