# ALBA-2022:0898: lvm2 bug fix and enhancement update

> Concurrent logical volume refresh operations may fail, potentially causing denial of service for local administrators managing storage.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Mar 2022

## What is ALBA-2022:0898?

ALBA-2022:0898 is a vulnerability in device-mapper-devel, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The lvm2 packages include complete support for handling read and write
operations on physical volumes, creating volume groups from one or more
physical volumes, and creating one or more logical volumes in volume
groups.

Bug Fix(es) and Enhancement(s):

* Multiple concurrent lv refreshes fail (BZ#2040514)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `device-mapper-devel` | AlmaLinux:8 | All versions | 8:1.02.177-11.el8_5 |
| `device-mapper-event-devel` | AlmaLinux:8 | All versions | 8:1.02.177-11.el8_5 |
| `lvm2-devel` | AlmaLinux:8 | All versions | 8:2.03.12-11.el8_5 |

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

Apply the vendor's patch.

## Is ALBA-2022:0898 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:0898 is a vulnerability in device-mapper-devel, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of ALBA-2022:0898 in the wild and no public exploit code.

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

## Sources

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

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