CVE-2023-33022
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 HLOS while invoking IOCTL calls from user-space.
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 High-Level Operating System (HLOS) kernel when handling IOCTL system calls invoked from user-space. This appears to be a local privilege escalation flaw where a user-space attacker can trigger memory corruption through specially crafted IOCTL requests, potentially gaining elevated privileges.
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 chipset modelCheck the device hardware specifications, /proc/cpuinfo, or modem AT command responses (e.g., ATI command) to determine the exact Qualcomm chipset (315 5G IoT, Aqt1000, Ar8035, Csra6620, Csra6640, Wcn3991, Wcn3998, or Wcn6750)Affected if The device contains any of the listed Qualcomm chipsets (315 5G IoT, Aqt1000, Ar8035, Csra6620, Csra6640, Wcn3991, Wcn3998, or Wcn6750)
-
Determine the firmware versionRetrieve the firmware version via AT commands (e.g., AT+CGMR, ATI), system information files, or vendor-specific diagnostic interfaces for the specific chipsetAffected if The firmware version cannot be determined or is from an unpatched release (all versions are initially affected)
-
Check for available security patchesConsult the vendor (Qualcomm or device OEM) security advisory for CVE-2023-33022 to confirm if a patch has been released for your specific firmware versionAffected if No vendor security patch for CVE-2023-33022 has been applied to your firmware version
-
Verify IOCTL interface exposureExamine if user-space applications can invoke IOCTL system calls against kernel drivers by reviewing /proc/devices, driver permissions, or SELinux policies restricting ioctl operationsAffected if User-space IOCTL access to kernel drivers is permitted without strict SELinux or seccomp restrictions
The device is affected if it contains any of the listed Qualcomm chipsets and the installed firmware lacks the CVE-2023-33022 security patch.
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 security patches (likely from Qualcomm or device OEM). Until patched, consider restricting device access, enforcing SELinux policies, and monitoring for suspicious IOCTL usage patterns.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33022 — 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-33022 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