# ALBA-2022:1548: device-mapper-multipath bug fix and enhancement update

> An update fixes missing start conditions for the multipathd socket in device-mapper-multipath, ensuring proper service initialization.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 26 Apr 2022

## What is ALBA-2022:1548?

ALBA-2022:1548 is a vulnerability in device-mapper-multipath-devel, published on 26 Apr 2022. 

### Official description

The device-mapper-multipath packages provide tools that use the device-mapper multipath kernel module to manage multipath devices.

Bug Fix(es) and Enhancement(s):

* multipathd.socket is missing start conditions (BZ#2054877)

## Which versions are affected by ALBA-2022:1548?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `device-mapper-multipath-devel` | AlmaLinux:8 | All versions | 0.8.4-17.el8_5.1 |

## How do I fix ALBA-2022:1548?

Apply the vendor's patch.

## Is ALBA-2022:1548 being exploited?

There is no known exploitation of ALBA-2022:1548 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2022:1548 and fix it if it is affected.

What it is: ALBA-2022:1548 is a vulnerability in device-mapper-multipath-devel, published on 26 Apr 2022. 
Exploitation: There is no known exploitation of ALBA-2022:1548 in the wild and no public exploit code.

Affected product: device-mapper-multipath-devel. 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/ALBA-2022-1548/ (Markdown: https://insights.sbomify.com/ALBA-2022-1548/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2022:1548

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