CVE-2020-8991
First published: Fri Feb 14 2020(Updated: )
** DISPUTED ** vg_lookup in daemons/lvmetad/lvmetad-core.c in LVM2 2.02 mismanages memory, leading to an lvmetad memory leak, as demonstrated by running pvs. NOTE: RedHat disputes CVE-2020-8991 as not being a vulnerability since there’s no apparent route to either privilege escalation or to denial of service through the bug.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| LVM2 | =2.02.00 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-8991?
The severity of CVE-2020-8991 is disputed by RedHat and is not classified as a critical vulnerability.
How does CVE-2020-8991 affect LVM2 versions?
CVE-2020-8991 affects LVM2 version 2.02.00 specifically, leading to potential memory leaks.
Is there a known exploit for CVE-2020-8991?
There are currently no known exploits associated with CVE-2020-8991.
How can I mitigate the impact of CVE-2020-8991?
Mitigation for CVE-2020-8991 involves updating LVM2 to the latest version to ensure any memory management issues are addressed.
What is the nature of the issue in CVE-2020-8991?
CVE-2020-8991 involves a memory leak in the vg_lookup function of LVM2, potentially leading to inefficient memory use.
- agent/type
- agent/references
- agent/severity
- agent/weakness
- agent/author
- agent/remedy
- agent/status
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- status/disputed
- vendor/redhat
- canonical/lvm2
- version/lvm2/2.02.00