CVE-2023-21650
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 in GPS HLOS Driver when injectFdclData receives data with invalid data length.
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 the GPS HLOS driver's injectFdclData function. The function fails to properly validate data length before processing input, allowing malformed data to corrupt memory.
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 GPS firmware modelQuery the system for the installed Qualcomm GPS firmware identifier (e.g., via 'at+cgmm', 'at+cgmodel', or system firmware tables)Affected if The model matches any of: Aqt1000, Csrb31024, Qam8295p, Qca6390, Qca6391, Qca6420, Qca6426, or Qca6430
-
Check GPS HLOS driver presenceInspect loaded kernel modules or driver list for the GPS HLOS driver (typically named 'gps', 'qcom_gps', or similar)Affected if The GPS HLOS driver module is loaded and active on the system
-
Verify injectFdclData function existsExamine the GPS driver binary or symbol table for the injectFdclData function entry pointAffected if The injectFdclData function is present in the loaded GPS driver
-
Check GPS data injection interface statusInspect GPS configuration or permissions files (e.g., /system/etc/gps.conf, SELinux policies, or GPS service status) to determine if data injection via injectFdclData is exposed or accessibleAffected if The data injection interface or FDCL feature is enabled or accessible to applications
-
Confirm driver version or patch levelQuery the GPS driver for its build date or version string, then compare against known patched releases from the Qualcomm product security bulletinAffected if The driver version predates the CVE-2023-21650 patch release date or no patch version is reported
The environment is affected if it uses any of the listed Qualcomm GPS firmware models and has the GPS HLOS driver with the injectFdclData function active, particularly if the data injection interface is enabled and the driver predates the patch release.
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 patch for CVE-2023-21650 to update the GPS HLOS driver with proper length validation in injectFdclData to prevent memory corruption from invalid-length input.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21650 — 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-21650 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