CVE-2025-21460
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 · uneditedMemory corruption while processing a message, when the buffer is controlled by a Guest VM, the value can be changed continuously.
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 confidenceMemory corruption vulnerability in hypervisor message processing where a Guest VM can control a buffer and continuously modify its value, likely indicating a Time-of-Check-to-Time-of-Use (TOCTOU) race condition that leads to memory corruption.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 the Qualcomm firmware variantCheck the system hardware documentation, bootloader, or firmware management interface to confirm the exact Qualcomm firmware model (Qam8255p, Qam8295p, Qam8620p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, or Qca6574a) is in useAffected if The system is running any of the listed firmware variants (Qam8255p, Qam8295p, Qam8620p, Qam8650p, Qam8775p, Qamsrv1h, Qamsrv1m, or Qca6574a)
-
Verify hypervisor component is activeQuery the firmware or hypervisor management interface to confirm the hypervisor subsystem is enabled and running. This may be accessible via hypervisor status commands, BMC/IPMI interfaces, or firmware diagnostic toolsAffected if The hypervisor component is enabled and processing VM messages
-
Confirm Guest VM functionality is enabledCheck the hypervisor configuration to determine if Guest VM instances can be created and are permitted to send messages to the hypervisor. Look for VM creation permissions or inter-VM communication settingsAffected if Guest VMs are permitted to run and can communicate with the hypervisor
-
Assess trust boundary for VM accessReview the access control policies or tenant configuration to determine whether untrusted or third-party Guest VMs have the ability to interact with the hypervisor message processing subsystemAffected if Untrusted or unknown Guest VMs can interact with the hypervisor
You are affected if your system runs any of the listed Qualcomm firmware variants with the hypervisor and Guest VM functionality enabled, particularly when untrusted VMs have access to the hypervisor message processing path.
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 patches for the affected hypervisor immediately; until patched, minimize exposure by restricting VM access to trusted tenants and monitoring for anomalous hypervisor behavior.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21460 — 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-2025-21460 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