CVE-2024-26328VulnerabilityPublished 19 Feb 2024Updated 6 Nov 2024

CVE-2024-26328: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-26328, organizations should take the following specific actions: 1) Monitor QEMU vendor advisories and security bulletins closely for patches addressing this vulnerability and apply them promptly once available. 2) Review and audit virtualization configurations to identify use of PCI SR-IOV with NVMe devices and assess exposure. 3) Limit high-privilege local access to trusted administrators only, employing strict access controls and monitoring to reduce the risk of insider threats. 4) Implement runtime monitoring of QEMU processes and virtual machine storage performance to detect anomalies indicative of denial of service conditions. 5) Consider temporarily disabling PCI SR-IOV features for NVMe devices in QEMU environments where feasible until patches are applied. 6) Employ network segmentation and isolation for management interfaces to prevent unauthorized local access. 7) Conduct regular security training for administrators on the risks of privilege misuse and the importance of patching virtualization infrastructure. These targeted measures go beyond generic advice by focusing on the specific components and access vectors involved in this vulnerability.

Description

An issue was discovered in QEMU 7.1.0 through 8.2.1.register_vfs in hw/pci/pcie_sriov.c does not set NumVFs to PCI_SRIOV_TOTAL_VF, and thus interaction with hw/nvme/ctrl.c is mishandled.

Impact

The primary impact of CVE-2024-26328 is on the availability of virtualized NVMe storage devices managed by QEMU in environments utilizing PCI SR-IOV. Exploitation could lead to denial of service conditions, causing virtual machines to lose access to critical storage resources, resulting in application downtime or system instability. Since confidentiality and integrity are not affected, data leakage or unauthorized data modification is unlikely. However, the disruption of storage availability can severely impact business operations, especially in cloud service providers, data centers, and enterprises relying on virtualized infrastructure for critical workloads. The requirement for local high-privilege access limits the attack surface to insiders or compromised administrative accounts, reducing the likelihood of remote exploitation but increasing risk from malicious insiders or attackers who have already gained elevated privileges. The scope change indicates that the vulnerability affects multiple components, potentially complicating detection and remediation. Organizations with heavy reliance on QEMU virtualization and SR-IOV-enabled NVMe devices may face operational risks, including service outages and degraded performance, until the vulnerability is addressed.

References

Community reviews

Loading reviews…