CVE-2023-3019: Red Hat Enterprise Linux 8 · Use After Free
Affects Red Hat Enterprise Linux 8Source CVE Database V5
Not known to be exploited · CVSS 6.0 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Jul 2023
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.
What to do
AI-suggested
To mitigate CVE-2023-3019, European organizations should: 1) Monitor Red Hat advisories and apply official patches or updates for Red Hat Enterprise Linux 8 and QEMU as soon as they become available. 2) Restrict privileged access within guest virtual machines to trusted administrators only, minimizing the risk of insider threats or compromised guest accounts. 3) Implement strict access controls and monitoring on virtualization hosts to detect unusual QEMU process crashes or guest VM behavior indicative of exploitation attempts. 4) Consider disabling or replacing the e1000e NIC emulation with alternative virtual NIC models if feasible and compatible with workloads. 5) Employ network segmentation and isolation for critical virtual machines to limit the blast radius of potential DoS attacks. 6) Regularly audit and update virtualization infrastructure configurations to follow security best practices recommended by Red Hat and QEMU communities. 7) Prepare incident response plans that include recovery procedures for QEMU process crashes to minimize downtime. These steps go beyond generic advice by focusing on access control, monitoring, and configuration adjustments specific to the vulnerability context.
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.
References
- access.redhat.com/errata/RHSA-2024:0135 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:0404 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:0569 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:2135 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2023-3019 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2222351 (opens in a new tab)
- security.netapp.com/advisory/ntap-20230831-0005/ (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/04/msg00042.html (opens in a new tab)