# CVE-2026-19617: Libdm: lvm2: libdm: denial of service via uncontrolled recursion in config parser

> A local attacker can cause a denial of service by crafting malicious LVM metadata that triggers uncontrolled recursion in the libdm parser.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Aug 2026
- **Updated:** 2 Oct 2026
- **Also known as:** AZL-96698, DEBIAN-CVE-2026-19617, ECHO-48b4-f133-d141, GHSA-2f2v-c79p-8x4x, RHSA-2026:73989, UBUNTU-CVE-2026-19617

## What is CVE-2026-19617?

CVE-2026-19617 is a medium-severity denial of service vulnerability in Redhat Enterprise Linux, published on 14 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in libdm. A local attacker could craft a malicious Logical Volume Manager (LVM) metadata configuration with deeply nested structures. This could lead to uncontrolled recursion in the libdm configuration file parser, exhausting the stack and causing any LVM command reading the metadata to crash. This vulnerability results in a Denial of Service (DoS) for affected systems.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-19617?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lvm2` | Red Hat:hummingbird:1 | All versions | 0:2.03.43-1.hum1 |
| `lvm2-dbusd` | Red Hat:hummingbird:1 | All versions | 0:2.03.43-1.hum1 |
| `lvm2-devel` | Red Hat:hummingbird:1 | All versions | 0:2.03.43-1.hum1 |
| `lvm2-libs` | Red Hat:hummingbird:1 | All versions | 0:2.03.43-1.hum1 |
| `lvm2-lockd` | Red Hat:hummingbird:1 | All versions | 0:2.03.43-1.hum1 |
| `lvm2-testsuite` | Red Hat:hummingbird:1 | All versions | 0:2.03.43-1.hum1 |

Products: Redhat Enterprise Linux, Redhat Hardened Images, Redhat Openshift Container Platform.

## How do I fix CVE-2026-19617?

Apply the vendor's patch.

## Is CVE-2026-19617 being exploited?

There is no known exploitation of CVE-2026-19617 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19617 and fix it if it is affected.

What it is: CVE-2026-19617 is a medium-severity denial of service vulnerability in Redhat Enterprise Linux, published on 14 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19617 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19617/ (Markdown: https://insights.sbomify.com/CVE-2026-19617/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19617
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19617
- OSV: https://osv.dev/vulnerability/CVE-2026-19617

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19617/
Summaries are generated and may contain mistakes; the official description above is the record.