Improper validation of array index in Multi-mode call processor

published 2023-03-07 3y ago modified 2026-06-17 4mo ago also EUVD-2022-36299

cvss: 9.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits: 0; none known

Memory corruption due to improper validation of array index in Multi-mode call processor.

Is CVE-2022-33256 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: last yr. (2025-03-05)

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Qualcomm, Inc. Snapdragon

Classification

Weakness

CWE-129 Improper Validation of Array Index

References

qualcomm.com /company/product-security/bulletins/march-2023-bulletin
vendor-advisory

Sources

CVE List CVE-2022-33256
NVD CVE-2022-33256

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.