Snapdragon: Access of Resource Using Incompatible Type
CVE-2023-28575 is a high-severity access of resource using incompatible type vulnerability in Snapdragon from Qualcomm, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Snapdragon versions: AQT1000; C-V2X 9150; FastConnect 6200, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.12% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Snapdragon you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on qualcomm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Qualcomm | Snapdragon | AQT1000; C-V2X 9150; FastConnect 6200; FastConnect 6800; FastConnect 6900; FastConnect 7800; QAM8295P; QCA6391; and 32 more ranges | Not stated |
| Qualcomm | Aqt1000 Firmware | Not specified in the record | Not stated |
| Qualcomm | C-v2x 9150 Firmware | Not specified in the record | Not stated |
| Qualcomm | Fastconnect 6200 Firmware | Not specified in the record | Not stated |
| Qualcomm | Fastconnect 6800 Firmware | Not specified in the record | Not stated |
| Qualcomm | Fastconnect 6900 Firmware | Not specified in the record | Not stated |
| Qualcomm | Fastconnect 7800 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qam8295p Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6391 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6420 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6426 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6430 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6436 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6574au Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca6696 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qca8337 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcn9074 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs410 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs610 Firmware | Not specified in the record | Not stated |
| Qualcomm | Qcs8155 Firmware | Not specified in the record | Not stated |
| Qualcomm | 205 Firmware | Not specified in the record | Not stated |
| Qualcomm | 215 Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6145p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6150p Firmware | Not specified in the record | Not stated |
| Qualcomm | Sa6155p Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.7 | Medium | CNA (qualcomm.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
The cam_get_device_priv function does not check the type of handle being returned (device/session/link). This would lead to invalid type usage if a wrong handle is passed to it.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Access of Resource Using Incompatible Type
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
More Access of Resource Using Incompatible Type vulnerabilities (CWE-843)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Snapdragon
- 7.1 High severity
- 7.0 High severity
Recent Access of Resource Using Incompatible Type vulnerabilities
- 8.1 High severity
- 8.8 High severity
- 8.1 High severity
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.