spi: bcm-qspi: return error if neither hif_mspi nor mspi is available
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 217b6ea8cf7b819477bca597a6ae2d43d38ba283, Kernel 22ae32d80ef590d12a2364e4621f90f7c58445c7, Kernel 32b9c8f7892c19f7f5c9fed5fb410b9fd5990bb6 and 5 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.9, >=fa236a7ef24048bafaeed13f68df35a819794758 <217b6ea8cf7b819477bca597a6ae2d43d38ba283, >=fa236a7ef24048bafaeed13f68df35a819794758 <22ae32d80ef590d12a2364e4621f90f7c58445c7, >=fa236a7ef24048bafaeed13f68df35a819794758 <32b9c8f7892c19f7f5c9fed5fb410b9fd5990bb6, >=fa236a7ef24048bafaeed13f68df35a819794758 <398e6a015877d44327f754aeb48ff3354945c78c, >=fa236a7ef24048bafaeed13f68df35a819794758 <7c1f23ad34fcdace50275a6aa1e1969b41c6233f, >=fa236a7ef24048bafaeed13f68df35a819794758 <a91c34357afcfaa5307e254f22a8452550a07b34, >=fa236a7ef24048bafaeed13f68df35a819794758 <d20db3c58a7f9361e370a7850ceb60dbdf62eea3, >=fa236a7ef24048bafaeed13f68df35a819794758 <d3dcdb43c872a3b967345144151a2c9bb9124c9b | 217b6ea8cf7b819477bca597a6ae2d43d38ba283, 22ae32d80ef590d12a2364e4621f90f7c58445c7, 32b9c8f7892c19f7f5c9fed5fb410b9fd5990bb6, 398e6a015877d44327f754aeb48ff3354945c78c, 7c1f23ad34fcdace50275a6aa1e1969b41c6233f, a91c34357afcfaa5307e254f22a8452550a07b34, d20db3c58a7f9361e370a7850ceb60dbdf62eea3, d3dcdb43c872a3b967345144151a2c9bb9124c9b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket