Memory corruption via unchecked GPU array index
Published Feb 3, 2025 · Updated Feb 3, 2025
Array-index validation failure in Qualcomm Snapdragon Graphics_Linux allows local users to corrupt memory through a crafted IOCTL. The GPU AHB bus-error handler fails to validate an array index before using it while servicing the user-space request. Low-privileged local access is required, and Qualcomm has not disclosed the exact out-of-bounds operation or resulting control-flow effects.
Summary
What happened
Array-index validation failure in Qualcomm Snapdragon Graphics_Linux allows local users to corrupt memory through a crafted IOCTL. The GPU AHB bus-error handler fails to validate an array index before using it while servicing the user-space request. Low-privileged local access is required, and Qualcomm has not disclosed the exact out-of-bounds operation or resulting control-flow effects.
The record
- CVE
- CVE-2024-49843
- Published
- Feb 3, 2025
- Updated
- Feb 3, 2025
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-129, CAPEC-100
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2025CVE publishedPublication date reported by the CVE source.
- Feb 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=FastConnect 6200
- Affected versionversion=FastConnect 7800
- Affected versionversion=QCA6391
- Affected versionversion=QCM6125
- Affected versionversion=QCS6125
- Affected versionversion=QCS7230
- Affected versionversion=QCS8250
- Affected versionversion=Qualcomm Video Collaboration VC1 Platform
- Affected versionversion=Qualcomm Video Collaboration VC5 Platform
- Affected versionversion=SM4635
- Affected versionversion=SM6650
- Affected versionversion=SM7635
- Affected versionversion=SM7675
- Affected versionversion=SM7675P
- Affected versionversion=SM8635
- Affected versionversion=SM8635P
- Affected versionversion=SM8750
- Affected versionversion=SM8750P
- Affected versionversion=Snapdragon 480 5G Mobile Platform
- Affected versionversion=Snapdragon 480+ 5G Mobile Platform (SM4350-AC)
- Affected versionversion=Snapdragon 4 Gen 1 Mobile Platform
- Affected versionversion=Snapdragon 695 5G Mobile Platform
- Affected versionversion=Snapdragon 8 Gen 3 Mobile Platform
- Affected versionversion=Snapdragon W5+ Gen 1 Wearable Platform
- Affected versionversion=SW5100
- Affected versionversion=SW5100P
- Affected versionversion=SXR2330P
- Affected versionversion=WCD9370
- Affected versionversion=WCD9375
- Affected versionversion=WCD9378
- Affected versionversion=WCD9380
- Affected versionversion=WCD9385
- Affected versionversion=WCD9390
- Affected versionversion=WCD9395
- Affected versionversion=WCN3950
- Affected versionversion=WCN3980
- Affected versionversion=WCN3988
- Affected versionversion=WCN6450
- Affected versionversion=WCN6650
- Affected versionversion=WCN6755
- Affected versionversion=WCN7860
- Affected versionversion=WCN7861
- Affected versionversion=WCN7880
- Affected versionversion=WCN7881
- Affected versionversion=WSA8810
- Affected versionversion=WSA8815
- Affected versionversion=WSA8830
- Affected versionversion=WSA8832
- Affected versionversion=WSA8835
- Affected versionversion=WSA8840
- Affected versionversion=WSA8845
- Affected versionversion=WSA8845H
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo