CVE-2024-41052

Userspace crash via uninitialized hot-reset device count

Published Jul 29, 2024 · Updated May 11, 2026

Use of an uninitialized variable in Linux 6.6.36 through 6.6.40 and 6.9.7 through 6.9.9 allows local users to crash VFIO userspace. The vfio_pci_ioctl_get_pci_hot_reset_info function passes an uninitialized stack count to vfio_pci_count_devs, so the result can drive an arbitrary allocation request or an undersized result buffer. Access to a VFIO PCI device file and the hot-reset-info ioctl is required; the documented consequence is caller disruption, including QEMU failure, rather than a host-kernel crash.

CVSS severity5.5
Medium
EPSS probability0.27%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use of an uninitialized variable in Linux 6.6.36 through 6.6.40 and 6.9.7 through 6.9.9 allows local users to crash VFIO userspace. The vfio_pci_ioctl_get_pci_hot_reset_info function passes an uninitialized stack count to vfio_pci_count_devs, so the result can drive an arbitrary allocation request or an undersized result buffer. Access to a VFIO PCI device file and the hot-reset-info ioctl is required; the documented consequence is caller disruption, including QEMU failure, rather than a host-kernel crash.

The record

CVE
CVE-2024-41052
Published
Jul 29, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-908, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 29, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record 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?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=618fbf4c910a06a3aa6a8b88a5fb1f2197f964f3 <f476dffc52ea70745dcabf63288e770e50ac9ab3
  2. Affected versionversion=6.6.36 <6.6.41
  3. Affected versionversion=6.9.7 <6.9.10
  4. Affected versionversion=9313244c26f3792daa86f3a18cc3bd5ad60310e0 <f44136b9652291ac1fc39ca67c053ac624d0d11b
  5. Affected versionversion=f6944d4a0b87c16bc34ae589169e1ded3d4db08e <5a88a3f67e37e39f933b38ebb4985ba5822e9eca

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=618fbf4c910a06a3aa6a8b88a5fb1f2197f964f3 <f476dffc52ea70745dcabf63288e770e50ac9ab3; version=6.6.36 <6.6.41; version=6.9.7 <6.9.10; version=9313244c26f3792daa86f3a18cc3bd5ad60310e0 <f44136b9652291ac1fc39ca67c053ac624d0d11b; version=f6944d4a0b87c16bc34ae589169e1ded3d4db08e <5a88a3f67e37e39f933b38ebb4985ba5822e9eca

Published CVSS scores

5.5NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-908Use of Uninitialized Resource
T1499Endpoint Denial of Service

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