CVE-2024-6519
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA use-after-free vulnerability was found in the QEMU LSI53C895A SCSI Host Bus Adapter emulation. This issue can lead to a crash or VM escape.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA use-after-free vulnerability exists in the QEMU LSI53C895A SCSI Host Bus Adapter emulation. This memory safety flaw occurs when memory is accessed after being freed, potentially allowing an attacker within a virtual machine to trigger the vulnerability and escape the VM or crash the host.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify QEMU installation and versionRun 'qemu-system-x86_64 --version' or 'qemu-system-aarch64 --version' (or other architecture variants) to determine the installed QEMU version. Also check 'which qemu-system-*' to find available QEMU binaries.Affected if Any QEMU version is installed using LSI53C895A SCSI emulation
-
Locate VM configurations using LSI SCSISearch VM configuration files (typically in /etc/libvirt/qemu/ for libvirt, or check VM XML definitions) for 'lsi53c895a' or 'LSI' in the <controller> or <devicemodel> sections. Also check QEMU command lines for '-device lsi53c895a' arguments.Affected if Any VM configuration explicitly uses lsi53c895a controller
-
Check default SCSI controller in useFor VMs configured with SCSI storage but no explicit controller specified, review the VM definition. Run 'virsh dumpxml <vmname>' for libvirt VMs and look for <model type='lsilogic'/> or similar SCSI controller models.Affected if VMs use LSI53C895A as the SCSI controller (common default for many VM templates)
-
Verify patch statusCompare installed QEMU version against vendor security advisories for CVE-2024-6519. Since all versions are affected, check if your distribution has released a patched version (typically noted in CVE data as 'fixed in version X.Y.Z').Affected if Installed version predates the CVE fix release date or lacks the specific security patch
A system is affected if it runs any QEMU version with LSI53C895A SCSI emulation enabled for virtual machines, and the installed QEMU version does not include the CVE-2024-6519 fix.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate QEMU to the patched version containing the CVE-2024-6519 fix. Since this is a host-side emulation vulnerability, patching the QEMU installation on the hypervisor protects all VMs using that host.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6519 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6519 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data