VulnerabilityPublished 18 Dec 2024Updated 20 Nov 2025

CVE-2024-11614: dpdk · Out-of-bounds Read

Affects dpdkSource CVE Database V5

Not known to be exploited · CVSS 7.4 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score

7.4High

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

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

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
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: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 18 Dec 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
Red Hatredhat/dpdk`pkg:rpm/redhat/dpdk`Other threats	Affected =21.05	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-11614, organizations should apply patches or updates provided by DPDK maintainers or their vendors as soon as they become available, especially for version 21.05 users. In the absence of immediate patches, administrators should consider restricting or isolating untrusted guest VMs that use virtio drivers to limit their ability to send malformed packets to the vhost-user interface. Network segmentation and strict access controls on management and virtual network interfaces can reduce exposure. Monitoring vSwitch logs and network traffic for unusual checksum offload requests or crashes can help detect exploitation attempts. Additionally, upgrading to newer, supported DPDK versions with security fixes and disabling unused checksum offload features in vhost-user configurations can reduce the attack surface. Implementing robust VM isolation and limiting privileges of guest VMs will further mitigate risks. Regular security assessments of virtualized network components are recommended to identify and remediate similar vulnerabilities proactively.

Description

An out-of-bounds read vulnerability was found in DPDK's Vhost library checksum offload feature. This issue enables an untrusted or compromised guest to crash the hypervisor's vSwitch by forging Virtio descriptors to cause out-of-bounds reads. This flaw allows an attacker with a malicious VM using a virtio driver to cause the vhost-user side to crash by sending a packet with a Tx checksum offload request and an invalid csum_start offset.

Impact

The primary impact of CVE-2024-11614 is denial of service caused by crashing the hypervisor's vSwitch component. This can lead to network outages or degraded performance for multiple virtual machines sharing the affected vSwitch, disrupting critical services and applications. In cloud environments or NFV infrastructures where DPDK is widely used for high-performance packet processing, this vulnerability could cause significant operational impact, including loss of connectivity, service interruptions, and potential cascading failures in dependent systems. Although the vulnerability does not directly compromise confidentiality or integrity, the resulting DoS can affect business continuity and availability of network services. Organizations relying on multi-tenant virtualization platforms or virtualized network functions are particularly at risk, as a compromised or malicious VM could intentionally trigger this flaw to disrupt other tenants or services. The ease of exploitation without authentication or user interaction increases the threat level in shared infrastructure environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 11:30 UTC

Technical details

References

Community reviews

Related threats