# ALBA-2022:1922: mdevctl bug fix and enhancement update

> The mdevctl utility in AlmaLinux's Linux kernel has a bug fix and enhancement update; AlmaLinux users should update.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Local or same network only
- **Victim action needed:** Not stated
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 10 May 2022

## What is ALBA-2022:1922?

ALBA-2022:1922 is an other vulnerability in mdevctl, published on 10 May 2022. It can only be exploited from the same machine or local network.

### Official description

The mdevctl package provides a utility for managing and persisting devices in the mediated device framework of the Linux kernel.

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

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mdevctl` | AlmaLinux:8 | All versions | 1.1.0-2.el8 |

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

Upgrade to a fixed version.

## Is ALBA-2022:1922 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:1922 is an other vulnerability in mdevctl, published on 10 May 2022. It can only be exploited from the same machine or local network.
Exploitation: There is no known exploitation of ALBA-2022:1922 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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