Snapdragon: Use After Free
CVE-2024-33034 is a high-severity use after free 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: FastConnect 6200; FastConnect 6700; FastConnect 6900, 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.1% 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 docs.qualcomm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Qualcomm | Snapdragon | FastConnect 6200; FastConnect 6700; FastConnect 6900; FastConnect 7800; Flight RB5 5G Platform; QAM8255P; QAM8295P; QAM8620P; and 32 more ranges | Not stated |
| Qualcomm | flight_rb5_5g_platform_firmware | all versions | Not stated |
| Qualcomm | qam8255p_firmware | all versions | Not stated |
| Qualcomm | qam8295p_firmware | all versions | Not stated |
| Qualcomm | qam8620p_firmware | all versions | Not stated |
| Qualcomm | qam8650p_firmware | all versions | Not stated |
| Qualcomm | qam8775p_firmware | all versions | Not stated |
| Qualcomm | qamsrv1h_firmware | all versions | Not stated |
| Qualcomm | qamsrv1m_firmware | all versions | Not stated |
| Qualcomm | qca6391_firmware | all versions | Not stated |
| Qualcomm | qca6574_firmware | all versions | Not stated |
| Qualcomm | qca6574a_firmware | all versions | Not stated |
| Qualcomm | qca6574au_firmware | all versions | Not stated |
| Qualcomm | qca6595_firmware | all versions | Not stated |
| Qualcomm | qca6595au_firmware | all versions | Not stated |
| Qualcomm | qca6678aq_firmware | all versions | Not stated |
| Qualcomm | qca6688aq_firmware | all versions | Not stated |
| Qualcomm | qca6696_firmware | all versions | Not stated |
| Qualcomm | qca6698aq_firmware | all versions | Not stated |
| Qualcomm | qca6797aq_firmware | all versions | Not stated |
| Qualcomm | qcm4325_firmware | all versions | Not stated |
| Qualcomm | qcm4490_firmware | all versions | Not stated |
| Qualcomm | qcm5430_firmware | all versions | Not stated |
| Qualcomm | qcm6125_firmware | all versions | Not stated |
| Qualcomm | qcm6490_firmware | all versions | 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 | 8.4 | High | CNA (qualcomm.com) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- 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 Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.