Memory corruption while registering a buffer from user-space to kernel-space using IOCTL calls.
CVE-2024-38411
Score 6.6 from GitHub Security Advisory published 2025-02-03. NVD baseline CVSS 6.6; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.6
- EG Score
- 6.6(medium)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity66% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
February 3, 2025
Last Modified
August 11, 2025
References (1)
- product-security@qualcommhttps://docs.qualcomm.com/product/publicresources/securitybulletin/february-2025-bulletin.html
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(5)
What is CVE-2024-38411?
When was CVE-2024-38411 disclosed?
Is CVE-2024-38411 actively exploited?
What is the CVSS score of CVE-2024-38411?
How do I remediate CVE-2024-38411?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-38411
Is Your Infrastructure Affected by CVE-2024-38411?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.