phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
368ea32e0ad0335bdf3180067875a928e35387c6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug
The qmp_usb_iomap() helper function currently returns the raw result of devm_ioremap() for non-exclusive mappings. Since devm_ioremap() may return a NULL pointer and the caller only checks error pointers with IS_ERR(), NULL could bypass the check and lead to an invalid dereference.
Fix the issue by checking if devm_ioremap() returns NULL. When it does, qmp_usb_iomap() now returns an error pointer via IOMEM_ERR_PTR(-ENOMEM), ensuring safe and consistent error handling.
From the CVE record · Linux
The Linux kernel’s qcom-qmp-usb driver can dereference a NULL pointer if a non-exclusive memory mapping fails. The input does not establish whether an attacker can trigger this failure or specify any authentication, network access, or user-interaction requirements.
Engineers running the Linux kernel should check whether their version includes the vulnerable qcom-qmp-usb code; affected versions are not specified.