CVE-2025-47380: Untrusted Pointer Dereference in Camera
Published Jan 6, 2026
·Updated
Memory corruption while preprocessing IOCTLs in sensors.
Affected Software
28 affected components
All of the following
Qualcomm Wsa8845h Firmware
Qualcomm Wsa8845h
All of the following
Qualcomm X2000077 Firmware
Qualcomm X2000077
All of the following
Qualcomm X2000086 Firmware
Qualcomm X2000086
All of the following
Qualcomm X2000090 Firmware
Qualcomm X2000090
All of the following
Qualcomm X2000092 Firmware
Qualcomm X2000092
All of the following
Qualcomm X2000094 Firmware
Qualcomm X2000094
All of the following
Qualcomm Xg101002 Firmware
Qualcomm Xg101002
All of the following
Qualcomm Xg101032 Firmware
Qualcomm Xg101032
All of the following
Qualcomm Xg101039 Firmware
Qualcomm Xg101039
All of the following
Qualcomm Fastconnect 7800 Firmware
Qualcomm Fastconnect 7800
All of the following
Qualcomm Qcc2072 Firmware
Qualcomm Qcc2072
All of the following
Qualcomm Wcd9378c Firmware
Qualcomm Wcd9378c
All of the following
Qualcomm Wsa8840 Firmware
Qualcomm Wsa8840
All of the following
Qualcomm Wsa8845 Firmware
Qualcomm Wsa8845
Event History
Jan 6, 2026
CVE Published
via MITRE·10:48 PM
Data Sourced
via MITRE·10:48 PM
DescriptionSeverityWeakness
Jan 7, 2026
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-47380?
CVE-2025-47380 is classified as a memory corruption vulnerability that can lead to potential exploitation.
2
How do I fix CVE-2025-47380?
To address CVE-2025-47380, you should update to the latest firmware version provided by Qualcomm.
3
Which devices are affected by CVE-2025-47380?
CVE-2025-47380 affects several Qualcomm firmware including the WSA8845H and WSA8840 among others.
4
What are the consequences of CVE-2025-47380?
Exploitation of CVE-2025-47380 may lead to untrusted pointer dereference resulting in possible system instability or data corruption.
5
Is there a known exploit for CVE-2025-47380?
As of now, there are no publicly known exploits for CVE-2025-47380, but it remains a risk until mitigated.