CVE-2024-51562
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 · uneditedThe NVMe driver function nvme_opc_get_log_page is vulnerable to a buffer over-read from a guest-controlled value.
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 · moderate confidenceThe NVMe driver function nvme_opc_get_log_page in a hypervisor suffers from a buffer over-read vulnerability where a guest-controlled value (likely an offset or length parameter in the NVMe Get Log Page command) is used without adequate bounds validation, allowing the guest to read beyond the allocated buffer boundary.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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 the hypervisor software in useDetermine which hypervisor platform is running (e.g., from vendor documentation, system logs, or /proc/sysinfo)Affected if The system is not a hypervisor (this CVE does not apply to non-hypervisor systems)
-
Identify the NVMe driver or module versionLocate the hypervisor's NVMe driver module and check its version (e.g., via lsmod, modinfo, or driver file properties)Affected if The NVMe driver version cannot be determined or is not listed as patched
-
Verify if NVMe virtualization is enabledCheck hypervisor configuration for enabled NVMe virtual devices, NVMe passthrough to VMs, or NVMe controller emulation featuresAffected if NVMe virtualization or passthrough is actively exposed to guest virtual machines
-
Check for guest-accessible NVMe devicesReview VM configurations to confirm whether any guests have assigned NVMe controllers or passthrough accessAffected if Guest virtual machines have NVMe device access
-
Compare installed version to fixed releasesIf the hypervisor vendor has published a security advisory for CVE-2024-51562, compare your installed version to the fixed version listedAffected if The installed version is older than the vendor-fixed version
A system is affected if it runs a hypervisor with a vulnerable NVMe driver version AND exposes NVMe virtual devices or passthrough to guest virtual machines, allowing guests to send NVMe Get Log Page commands with unchecked parameters.
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 dataApply vendor-provided patches to the hypervisor's NVMe driver that add proper bounds checking on guest-supplied offset and length parameters before buffer access.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51562 — 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-51562 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