CVE-2026-89329
Device-mapper-multipath: local denial of service via blocking ipc send operations
What happened?
A flaw was found in `multipathd`. A local attacker with access to the `multipathd` UNIX control socket can exploit this vulnerability by sending valid commands and then ceasing to read replies. This action can cause the `multipathd` listener thread to block, leading to a Denial of Service (DoS) where legitimate Inter-Process Communication (IPC) operations may hang or time out. This issue does not result in privilege escalation, arbitrary code execution, or impact data confidentiality or integrity.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| device-mapper-multipathRed Hat | Default status: affected | See vendor advisory |
| device-mapper-multipathRed Hat | Default status: unknown | See vendor advisory |
| device-mapper-multipathRed Hat | Default status: affected | See vendor advisory |
| device-mapper-multipathRed Hat | Default status: affected | See vendor advisory |
| device-mapper-multipathRed Hat | Default status: affected | See vendor advisory |
| openshift/ose-rhel-coreos-8Red Hat | Default status: affected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: affected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.