Daemon crash via off-by-one interface-name write
Published Mar 11, 2024 · Updated Nov 8, 2025
Off-by-one error in libvirt 9.7.0 allows local users to crash the libvirt daemon through crafted interface-list API requests. udevListInterfacesByStatus() accepts count equal to names_len and writes one additional interface name, including a null-pointer dereference for a zero-length null array. Unprivileged local client access is sufficient; the demonstrated consequence is interruption of virtualization management, not privilege gain or code execution.
Summary
What happened
Off-by-one error in libvirt 9.7.0 allows local users to crash the libvirt daemon through crafted interface-list API requests. udevListInterfacesByStatus() accepts count equal to names_len and writes one additional interface name, including a null-pointer dereference for a zero-length null array. Unprivileged local client access is sufficient; the demonstrated consequence is interruption of virtualization management, not privilege gain or code execution.
The record
- CVE
- CVE-2024-1441
- Published
- Mar 11, 2024
- Updated
- Nov 8, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-193, T1489
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Nov 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo