Use-After-Free in Qualcomm Sa6150P Firmware (CVE-2025-47333)
Summary
Vulnerability in Qualcomm Sa6150P Firmware (CVE-2025-47333). Data can be tampered with by attackers.
Original description
The description as published by the source.
Memory corruption while handling buffer mapping operations in the cryptographic driver.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2025-47333 was discovered in Qualcomm Sa6150P Firmware.
In plain terms, it is a use-after-free flaw that often leads to attacker takeover.
Severity is Medium (CVSS 6.6/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Qualcomm Sa6150P Firmware CVE-2025-47333".
CVE-2025-47333 (Qualcomm Sa6150P Firmware). Severity: Medium / CVSSv3 6.6. Category: CWE-416.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2025-47333) in Qualcomm Sa6150P Firmware. In plain words, it is a use-after-free flaw that often leads to attacker takeover.
Target versions of Qualcomm Sa6150P Firmware (see vendor advisory). If running in production, identify exposure immediately.
Severity: Medium (CVSS 6.6/10). Exploitation requires specific conditions but can cause real harm if successful.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-416)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.