Security readout for executives and security teams
Plain-English summary
This Qualcomm vulnerability affects listed Snapdragon-related platforms and can corrupt memory inside the Trusted Execution Environment during license validation cleanup. A local, low-privileged attacker could potentially affect sensitive protected execution areas. The business risk is highest for managed device, embedded, automotive, robotics, and edge fleets using affected Qualcomm components.
Executive priority
Treat this as a high-priority firmware exposure review for Qualcomm-based fleets, especially where devices are shared, unmanaged, field-deployed, or safety-sensitive. The absence of KEV evidence lowers immediate exploitation urgency, but TEE memory corruption can carry serious confidentiality and integrity consequences.
Technical view
CVE-2023-33046 is a CWE-367 time-of-check/time-of-use race condition causing memory corruption in Qualcomm's Trusted Execution Environment while deinitializing an object used for license validation. CVSS 3.1 is 7.8 with local access, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure depends on whether devices contain one of the listed Qualcomm Snapdragon, FastConnect, QCA, QCM, QCS, QRB, SA, SG, SSG, SXR, WCD, or WSA components. Most organizations will validate exposure through device OEM firmware advisories, not by inspecting Qualcomm silicon directly.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The CVSS vector indicates exploitation requires local access and low privileges, without user interaction. Public sources here do not establish remote exploitation or provide exploit status beyond the vendor and CVE records.
Researcher notes
Focus analysis on the TEE license-validation deinitialization path and TOCTOU race handling. The provided sources identify the affected product families and impact class, but do not include exploit details, patch implementation specifics, or compensating controls. Do not infer affected OEM devices without chipset or advisory evidence.
Mitigation direction
- Check Qualcomm's February 2024 bulletin for vendor guidance and affected platform details.
- Check device OEM advisories for firmware or security updates referencing CVE-2023-33046.
- Prioritize affected managed, embedded, automotive, robotics, and edge devices with local user access.
- Track update availability for devices using affected Qualcomm components.
- Avoid assuming one OEM's fix status applies to another device model.
Validation and detection
- Inventory device models and chipsets against the affected Qualcomm product list.
- Confirm whether OEM firmware notes reference CVE-2023-33046 or Qualcomm February 2024 fixes.
- Record devices with listed components but no available OEM remediation guidance.
- Validate that deployed firmware matches the OEM's remediated release when available.
- Document unaffected status only when chipset or OEM evidence supports it.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-33046 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.