How to Fix CVE-2023-33106: Use of Out-of-range Pointer Offset in Qualcomm, Inc. Snapdragon
By Sai Kiran Pandrala
| Severity | CVSS 8.4 (High) |
|---|---|
| Actively exploited? | Yes, listed in CISA KEV (added 2023-12-05, federal due date 2023-12-26) |
| Affected | Snapdragon: AR8035, CSRA6620, CSRA6640, FastConnect 6200, FastConnect 6700, FastConnect 6800, FastConnect 6900, FastConnect 7800, Flight RB5 5G Platform, QAM8255P, QAM8295P, QAM8650P, QAM8775P, QCA6174A, QCA6391, QCA6426, QCA6436, QCA6574, QCA6574A, QCA6574AU, QCA6595, QCA6595AU, QCA6696, QCA6698AQ, QCA6797AQ, QCA8081, QCA8337, QCA9377, QCM2290, QCM4290, QCM4325, QCM4490, QCM5430, QCM6490, QCM8550, QCN6024, QCN9011, QCN9012, QCN9024, QCS2290, QCS410, QCS4290, QCS4490, QCS5430, QCS610, QCS6490, QCS7230, QCS8250, QCS8550, QRB5165M, QRB5165N, Qualcomm 215 Mobile Platform, Qualcomm Video Collaboration VC1 Platform, Qualcomm Video Collaboration VC3 Platform, Qualcomm Video Collaboration VC5 Platform, Robotics RB5 Platform, SA4150P, SA4155P, SA6145P, SA6150P, SA6155P, SA8145P, SA8150P, SA8155P, SA8195P, SA8255P, SA8295P, SA8770P, SA8775P, SA9000P, SD 8 Gen1 5G, SD660, SD865 5G, SD888, SG4150P, SG8275P, SM4125, SM7250P, SM7315, SM7325P, SM8550P, Smart Audio 400 Platform, Snapdragon 4 Gen 1 Mobile Platform, Snapdragon 4 Gen 2 Mobile Platform, Snapdragon 439 Mobile Platform, Snapdragon 460 Mobile Platform, Snapdragon 480 5G Mobile Platform, Snapdragon 480+ 5G Mobile Platform (SM4350-AC), Snapdragon 660 Mobile Platform, Snapdragon 662 Mobile Platform, Snapdragon 680 4G Mobile Platform, Snapdragon 685 4G Mobile Platform (SM6225-AD), Snapdragon 690 5G Mobile Platform, Snapdragon 695 5G Mobile Platform, Snapdragon 750G 5G Mobile Platform, Snapdragon 765 5G Mobile Platform (SM7250-AA), Snapdragon 765G 5G Mobile Platform (SM7250-AB), Snapdragon 768G 5G Mobile Platform (SM7250-AC), Snapdragon 778G 5G Mobile Platform, Snapdragon 778G+ 5G Mobile Platform (SM7325-AE), Snapdragon 780G 5G Mobile Platform, Snapdragon 782G Mobile Platform (SM7325-AF), Snapdragon 7c+ Gen 3 Compute, Snapdragon 8 Gen 1 Mobile Platform, Snapdragon 8 Gen 2 Mobile Platform, Snapdragon 8+ Gen 1 Mobile Platform, Snapdragon 8+ Gen 2 Mobile Platform, Snapdragon 865 5G Mobile Platform, Snapdragon 865+ 5G Mobile Platform (SM8250-AB), Snapdragon 870 5G Mobile Platform (SM8250-AC), Snapdragon 888 5G Mobile Platform, Snapdragon 888+ 5G Mobile Platform (SM8350-AC), Snapdragon AR2 Gen 1 Platform, Snapdragon Auto 5G Modem-RF, Snapdragon W5+ Gen 1 Wearable Platform, Snapdragon X12 LTE Modem, Snapdragon X55 5G Modem-RF System, Snapdragon X65 5G Modem-RF System, Snapdragon XR2 5G Platform, Snapdragon XR2+ Gen 1 Platform, SSG2115P, SSG2125P, SW5100, SW5100P, SXR1230P, SXR2130, SXR2230P, WCD9326, WCD9335, WCD9341, WCD9370, WCD9375, WCD9380, WCD9385, WCD9390, WCD9395, WCN3615, WCN3660B, WCN3680B, WCN3910, WCN3950, WCN3980, WCN3988, WCN3990, WCN6740, WSA8810, WSA8815, WSA8830, WSA8832, WSA8835, WSA8840, WSA8845, WSA8845H |
| Fixed in | See vendor advisory for the patched build for your version |
| Type (CWE) | CWE-823 — Use of Out-of-range Pointer Offset |
This advisory bundle also covers: CVE-2023-33107, CVE-2023-33063. The patched build below closes all sibling CVEs in the same vendor release.
What is CVE-2023-33106?
Memory corruption while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.
A successful exploit gives the attacker the impact described in the vendor advisory. The fix is to install the patched build from Qualcomm, Inc. listed in the table above and confirm the running version after the upgrade.
Am I affected?
Check your installed version of Qualcomm, Inc. Snapdragon against the Affected row above. If your build sits within any of those ranges, treat the system as vulnerable until patched.
If you do not have the version handy, pull it the same way you usually would for Snapdragon: the management console's About page, the CLI's version command, or the package manager record for the installed binary. The vendor advisory linked in the references section is the authoritative source.
How to fix CVE-2023-33106
- Read the vendor advisory at https://www.qualcomm.com/company/product-security/bulletins/december-2023-bulletin for the build matrix that matches your installation.
- Identify the patched build for your major version from the advisory's downloads section.
- Back up configuration before upgrading (export running config, snapshot the VM, or take a database dump as appropriate for your platform).
- Apply the patched build using the vendor's documented upgrade path (in-place upgrade, package update, or replacement image).
- Restart the service so the new code is loaded; verify the running version reports the patched build number.
Patch via your OS package manager
# The exact package name and patched version are listed in the vendor advisory:
# https://www.qualcomm.com/company/product-security/bulletins/december-2023-bulletin
# Debian / Ubuntu
sudo apt update
sudo apt install --only-upgrade snapdragon
# RHEL / Rocky / AlmaLinux / Fedora
sudo dnf upgrade snapdragon
# openSUSE
sudo zypper update snapdragon
# Verify the running version matches the fixed version
dpkg -s snapdragon 2>/dev/null | grep -i version || rpm -q snapdragon 2>/dev/null
# Windows: pull the cumulative update that ships this fix.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck
Get-WindowsUpdate -AcceptAll -Install -AutoReboot
Verify the fix landed
# 1. Confirm the running version matches the fixed-in version from the advisory:
# https://www.qualcomm.com/company/product-security/bulletins/december-2023-bulletin
# Use the platform-specific version probe above.
# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
# The scanner should no longer flag CVE-2023-33106 on the patched target.
# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"
If you can't patch immediately
Check the vendor advisory's "Workarounds" section. If the advisory lists no official workaround, patching is the only remediation. Compensating controls that reduce attack surface in the meantime: restrict network access to the management interface to a small admin allowlist, disable the affected feature if it is not in use, and monitor the relevant logs for the exploitation patterns referenced in the advisory.
How to verify the fix worked
- Confirm the running version matches the patched build from the vendor advisory.
- Re-run your vulnerability scanner; the CVE should clear.
- Review logs from before the patch for the exploitation signatures described in the advisory, and treat any matches as a possible compromise (rotate credentials, isolate the host, full IR).
Frequently asked questions
Is CVE-2023-33106 being exploited right now?
Yes. It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-12-05), which means CISA has evidence of active exploitation.
What is the CVSS score for CVE-2023-33106?
CVSS 8.4 (High). Use this with your own asset exposure to set patching priority (internet-exposed systems first).
Do I need to take the system offline to patch?
It depends on the platform. Many appliances support hitless upgrade in HA pairs (upgrade standby, fail over, upgrade primary). Servers and applications usually need a service restart. Plan a maintenance window if HA is not available.
What if my version is not listed as affected?
Cross-check against the vendor advisory linked below. The CVE record reflects the vendor's official affected-products list at publication time; later-discovered variants are added through the same advisory or a follow-up CVE.
References
- Official vendor advisory: https://www.qualcomm.com/company/product-security/bulletins/december-2023-bulletin
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33106
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
*This guide was assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*