nday
CVE-2023-33107

Integer Overflow or Wraparound in Graphics Linux

Qualcomm / Multiple Chipsets · Qualcomm, Inc. / Snapdragon

Added to CISA KEV on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

integer overflow
CWE-190, stated by the CNA qualcomm, NVD's analysts, and NVD, republishing [email protected]
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA qualcomm
no authentication required
PR:N in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA qualcomm
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA qualcomm
Qualcomm Snapdragon
affected products in the CVE record: Qualcomm, Inc. · SnapdragonCPE names NVD's analysts give as vulnerable: o:qualcomm:apq8017_firmware, o:qualcomm:apq8064au_firmware, o:qualcomm:mdm9250_firmware, o:qualcomm:mdm9650_firmware, o:qualcomm:msm8108_firmware, o:qualcomm:msm8209_firmware, o:qualcomm:msm8608_firmware, o:qualcomm:msm8909w_firmware, o:qualcomm:msm8996au_firmware, o:qualcomm:sd626_firmware and 94 more
chipset / firmware
affected products in the CVE record: Qualcomm · Multiple Chipsets, Qualcomm, Inc. · SnapdragonCPE names NVD's analysts give as vulnerable: o:qualcomm:315_5g_iot_modem_firmware, o:qualcomm:apq8017_firmware, o:qualcomm:apq8064au_firmware, o:qualcomm:aqt1000_firmware, o:qualcomm:ar8031_firmware, o:qualcomm:ar8035_firmware, o:qualcomm:c-v2x_9150_firmware, o:qualcomm:csra6620_firmware, o:qualcomm:csra6640_firmware, o:qualcomm:csrb31024_firmware and 232 morethe product type of Qualcomm Snapdragon in nday's product registrynday's type rule vendor:qualcomm
stage
KEV
disclosed
cvss
8.4 HIGH v3.1
KEV due date
2023-12-26

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2023-12-05T03:04Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 2023-12-05, inferred from KEV
KEVKEV
2023-12-05, date only

Summary

Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA qualcomm.

Event log

2023-12-05date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2023-12-26. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 732,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2023-12-05T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-190"
    ],
    "notes": "This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see: https://git.codelinaro.org/clo/la/kernel/msm-4.19/-/commit/d66b799c804083ea5226cfffac6d6c4e7ad4968b;  https://nvd.nist.gov/vuln/detail/CVE-2023-33107",
    "product": "Multiple Chipsets",
    "due_date": "2023-12-26",
    "precision": "day",
    "date_added": "2023-12-05",
    "vendor_project": "Qualcomm",
    "forensic_triage": "No",
    "required_action": "Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.",
    "vulnerability_name": "Qualcomm Multiple Chipsets Integer Overflow Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2023-12-05inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

+DISdisclosed

CVE record published by qualcomm. CVSS 8.4, high. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17296,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2023-33107",
  "occurred_at": "2023-12-05T03:04:29.196Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-33107",
      "date_added": "2023-12-05"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.4,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2023-12-07T05:00:08.151868Z",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2023-12-05T03:04:29.196Z",
    "assigner_short_name": "qualcomm"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.