Daemon memory consumption via unreleased volume-group lookups
Published Feb 14, 2020 · Updated Aug 4, 2024
Memory leakage in LVM2 2.02 lvmetad allows local users with root privileges to consume daemon memory by repeatedly running pvs. The vg_lookup function in daemons/lvmetad/lvmetad-core.c fails to release memory associated with repeated volume-group lookups. Only root can reach lvmetad in the standard configuration, and Red Hat disputes any denial-of-service or privilege-escalation path because the optional cache can be killed, disabled, or bypassed.
Summary
What happened
Memory leakage in LVM2 2.02 lvmetad allows local users with root privileges to consume daemon memory by repeatedly running pvs. The vg_lookup function in daemons/lvmetad/lvmetad-core.c fails to release memory associated with repeated volume-group lookups. Only root can reach lvmetad in the standard configuration, and Red Hat disputes any denial-of-service or privilege-escalation path because the optional cache can be killed, disabled, or bypassed.
The record
- CVE
- CVE-2020-8991
- Published
- Feb 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo