# CVE-2024-1441: Libvirt: off-by-one error in udevlistinterfacesbystatus()

> An off-by-one error in libvirt allows unprivileged clients to crash the daemon via crafted data, causing denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2024
- **Updated:** 8 Nov 2025
- **Also known as:** AZL-35848, AZL-38602, BELL-CVE-2024-1441, DEBIAN-CVE-2024-1441, GHSA-2cj9-wjmr-5w57, UBUNTU-CVE-2024-1441, openSUSE-SU-2024:13759-1

## What is CVE-2024-1441?

CVE-2024-1441 is a medium-severity vulnerability in Red Hat Enterprise Linux 6, published on 11 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An off-by-one error flaw was found in the udevListInterfacesByStatus() function in libvirt when the number of interfaces exceeds the size of the `names` array. This issue can be reproduced by sending specially crafted data to the libvirt daemon, allowing an unprivileged client to perform a denial of service attack by causing the libvirt daemon to crash.

Weakness: CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2024-1441?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libvirt` | openSUSE:Tumbleweed | All versions | 10.1.0-1.1 |

## How do I fix CVE-2024-1441?

Apply the vendor's patch.

## Is CVE-2024-1441 being exploited?

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

Public exploit code:

- https://github.com/almkuznetsov/CVE-2024-1441 (github_poc): https://github.com/almkuznetsov/CVE-2024-1441

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1441 and fix it if it is affected.

What it is: CVE-2024-1441 is a medium-severity vulnerability in Red Hat Enterprise Linux 6, published on 11 Mar 2024. 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 CVE-2024-1441 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. 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-2024-1441/ (Markdown: https://insights.sbomify.com/CVE-2024-1441/index.md)
```

## Sources

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

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