CVE-2022-22071
Qualcomm
KEV
- Vendors: Qualcomm
This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see: https://git.codelinaro.org/clo/la/kernel/msm-5.4/-/commit/586840fde350d7b8563df9889c8ce397e2c20dda; https://nvd.nist.gov/vuln/detail/CVE-2022-22071
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
- CVE-1999-0006 (CVSS 9.8)
- CVE-2000-0342 (CVSS 7.5)
- CVE-2000-0320 (no score)
- CVE-1999-0427 (no score)
- CVE-2000-0442 (no score)
- CVE-1999-1448 (no score)
- CVE-1999-1016 (no score)
- CVE-1999-0822 (no score)
- CVE-2000-0096 (no score)
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2022-22071
CVE-2022-22071 is a unknown severity vulnerability affecting Qualcomm the affected product.
Description: This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see: https://git.codelinaro.org/clo/la/kernel/msm-5.4/-/commit/586840fde350d7b8563df9889c8ce397e2c20dda; https://nvd.nist.gov/vuln/detail/CVE-2022-22071 Related CVE by CWENo related CWE found.Top CVE for VendorCVE-1999-0006 (CVSS 9.8)CVE-2000-0342 (CVSS 7.5)CVE-2000-0320 (no score)CVE-1999-0427 (no score)CVE-2000-0442 (no score)CVE-1999-1448 (no score)CVE-1999-1016 […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running the affected product
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Vendor Advisory: https://git.codelinaro.org/clo/la/kernel/msm-5.4/-/commit/586840fde350d7b8563df9889c8ce397e2c20dda;
Description: This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see: https://git.codelinaro.org/clo/la/kernel/msm-5.4/-/commit/586840fde350d7b8563df9889c8ce397e2c20dda; https://nvd.nist.gov/vuln/detail/CVE-2022-22071 Related CVE by CWENo related CWE found.Top CVE for VendorCVE-1999-0006 (CVSS 9.8)CVE-2000-0342 (CVSS 7.5)CVE-2000-0320 (no score)CVE-1999-0427 (no score)CVE-2000-0442 (no score)CVE-1999-1448 (no score)CVE-1999-1016 […]
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
1 Identify affected systems
- Check if you're running the affected product
2 Immediate actions
- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
3 Verification
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
4 Long-term prevention
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Vendor Advisory: https://git.codelinaro.org/clo/la/kernel/msm-5.4/-/commit/586840fde350d7b8563df9889c8ce397e2c20dda;
Exploit Difficulty Assessment
HARD
Time to Exploit: > 4 hours
Skills Required: Advanced security expertise
Public Exploits: Rare or not public
KEV Status: This vulnerability is actively exploited in the wild!
Vulnerability Timeline
Timeline information not available for this CVE.
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.