CVE-2023-3019

Qemu: e1000e: heap use-after-free in e1000e_write_packet_to_guest()

MEDIUM
6.5
CVSS Score
Published: July 24, 2023 at 03:19 PM UTC
Updated: June 17, 2026 at 06:13 AM UTC
14 products affected across 3 vendorsEnterprise LinuxQEMURUGGEDCOM Rox RX1510 Firmware

Using Red Hat Enterprise Linux 8 by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat Enterprise Linux 8 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

A DMA reentrancy issue leading to a use-after-free error was found in the e1000e NIC emulation code in QEMU. This issue could allow a privileged guest user to crash the QEMU process on the host, resulting in a denial of service.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 8.2.0
Affected range stops below 8.2.0, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 17:8.2.0-11.el9_4 (unaffected)
Vendor states this is fixed in 8060020231128234847.ad008a3a (unaffected)
Vendor states this is fixed in 8080020240116113044.63b34585 (unaffected)
Vendor states this is fixed in 8090020231206155326.a75119d5 (unaffected)
Vendor states this is fixed in 6 (unknown)
Vendor states this is fixed in 7 (unknown)
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement

References (9)

Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:0135
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:0404
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2024:0569
VDB Entryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/security/cve/CVE-2023-3019
Issue Trackingx_refsource_REDHATPatchThird Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=2222351
Source: af854a3a-2127-422b-91ae-364da2661108
https://security.netapp.com/advisory/ntap-20230831-0005/
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/04/msg00042.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card