Loading vulnerability…
CVE-2025-38275 is a Linux kernel vulnerability in the Qualcomm QMP USB PHY driver. The flaw is in the qmp_usb_iomap() helper, which returned the raw result of devm_ioremap() for non-exclusive mappings. Because devm_ioremap() can return NULL on failure, while the caller validated only error pointers with IS_ERR(), a NULL return could bypass the existing error check. This mismatch in error-handling semantics could subsequently lead to an invalid NULL pointer dereference in the qcom-qmp-usb code path. The fix changes qmp_usb_iomap() to detect NULL returns from devm_ioremap() and convert them into an error pointer using IOMEM_ERR_PTR(-ENOMEM), ensuring consistent handling by callers.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.