CVE-2023-21673
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 · uneditedImproper Access to the VM resource manager can lead to Memory Corruption.
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 confidenceImproper access control in the VM resource manager allows an attacker to trigger memory corruption. The vulnerability stems from insufficient authorization checks when accessing virtual machine resource allocation functions, potentially enabling a local or authenticated attacker to corrupt memory and possibly execute arbitrary code.
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 Qualcomm firmware componentsInventory the system for presence of Qualcomm Aqt1000, Ar8035, Fastconnect 6200/6700/6800/6900/7800, or Flight Rb5 5g components. Check device/hardware manifests, firmware images, or system information interfaces that list installed chipset firmware.Affected if Any of the listed Qualcomm firmware components are present in the environment
-
Confirm VM resource management is in useDetermine whether the system utilizes VM (virtual machine) resource management functionality. This may be indicated by virtualization platforms, hypervisor configurations, or firmware management interfaces that expose resource allocation controls for virtual machines.Affected if VM resource management features are enabled or accessible on the system
-
Verify access controls on VM resource allocation interfacesReview the configuration and authorization settings for VM resource allocation functions. Check whether the VM resource manager enforces proper authorization checks before allowing access to memory allocation or resource manipulation functions.Affected if VM resource allocation functions lack proper authorization enforcement or allow unrestricted access
-
Inspect for memory corruption indicatorsMonitor system logs, memory dump files, or crash reports for signs of memory corruption that may stem from unauthorized VM resource manipulation. Check for unexpected memory allocations, buffer overflows, or abnormal memory patterns in contexts involving VM resource management.Affected if Memory corruption patterns are observed in VM-related operations or memory management subsystems
The environment is affected if any of the listed Qualcomm firmware components are present and the system utilizes VM resource management functionality without having applied vendor patches.
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 for the virtualization platform. If no patch is available, restrict administrative/root access to the VM resource management interfaces and monitor for unauthorized resource manipulation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21673 — 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-2023-21673 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