CVE-2023-53658: spi: bcm-qspi: return error if neither hif_mspi nor mspi is available

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-10-07 · updated 2026-10-28
Weakness: CWE-476

Description

In the Linux kernel, the following vulnerability has been resolved: spi: bcm-qspi: return error if neither hif_mspi nor mspi is available If neither a "hif_mspi" nor "mspi" resource is present, the driver will just early exit in probe but still return success. Apart from not doing anything meaningful, this would then also lead to a null pointer access on removal, as platform_get_drvdata() would return NULL, which it would then try to dereference when trying to unregister the spi master. Fix this by unconditionally calling devm_ioremap_resource(), as it can handle a NULL res and will then return a viable ERR_PTR() if we get one. The "return 0;" was previously a "goto qspi_resource_err;" where then ret was returned, but since ret was still initialized to 0 at this place this was a valid conversion in 63c5395bb7a9 ("spi: bcm-qspi: Fix use-after-free on unbind"). The issue was not introduced by this commit, only made more obvious.

Affected products

Linux kernel: from 4.9 before 4.14.322; from 4.15 before 4.19.291; from 4.20 before 5.4.251; from 5.5 before 5.10.188; from 5.11 before 5.15.121; from 5.16 before 6.1.39 — fixed in 4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.39

How to fix

Upgrade to a fixed version: Linux kernel 4.14.322, 4.19.291, 5.4.251, 5.10.188. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2023-53658 or the next vulnerability affects your stack