LVM command crashes via recursive metadata parsing
Published Aug 14, 2026 · Updated Aug 14, 2026
Uncontrolled recursion in libdm allows local users to crash LVM commands on affected Red Hat Enterprise Linux and OpenShift systems. The libdm configuration-file parser descends through deeply nested LVM metadata structures without bounding recursion, exhausting the process stack. Exploitation requires the ability to create or modify LVM metadata, such as on untrusted shared or externally attached storage, and interrupts any command that reads it.
Summary
What happened
Uncontrolled recursion in libdm allows local users to crash LVM commands on affected Red Hat Enterprise Linux and OpenShift systems. The libdm configuration-file parser descends through deeply nested LVM metadata structures without bounding recursion, exhausting the process stack. Exploitation requires the ability to create or modify LVM metadata, such as on untrusted shared or externally attached storage, and interrupts any command that reads it.
The record
- CVE
- CVE-2026-19617
- Published
- Aug 14, 2026
- Updated
- Aug 14, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 6
- Classifications
- CWE-770, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2026CVE publishedPublication date reported by the CVE source.
- Aug 14, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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