spi: bcm-qspi: return error if neither hif_mspi nor mspi is available
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.322, 4.19.291, 5.10.188, 5.15.121, 5.4.251, 6.1.39, 6.4.4
- CVEs
- CVE-2023-53658
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 07:56 UTC · Revision 1
Source evidence
spi: bcm-qspi: return error if neither hif_mspi nor mspi is available
core-osv · Original sourcePublished 7 Oct 2025, 15:21 UTC
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.
osv:CVE-2023-53658
Kernel
Fixed versions: 4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.39, 6.4.4
Complete source record
{
"id": "3f9ca0347aa36262287901f1b711e9655c531c9d515c3fa9ade1cf4a8a4e59e1",
"url": "https://osv.dev/vulnerability/CVE-2023-53658",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "spi: bcm-qspi: return error if neither hif_mspi nor mspi is available",
"summary": "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.",
"evidence": "osv:CVE-2023-53658",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.14.322",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.291",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.251",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.188",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.121",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.39",
"evidence": "/affected/1/ranges"
},
{
"value": "6.4.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2023-53658",
"aliases": [
"CVE-2023-53658"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "fa236a7ef24048bafaeed13f68df35a819794758"
},
{
"fixed": "a91c34357afcfaa5307e254f22a8452550a07b34"
},
{
"fixed": "d20db3c58a7f9361e370a7850ceb60dbdf62eea3"
},
{
"fixed": "398e6a015877d44327f754aeb48ff3354945c78c"
},
{
"fixed": "32b9c8f7892c19f7f5c9fed5fb410b9fd5990bb6"
},
{
"fixed": "217b6ea8cf7b819477bca597a6ae2d43d38ba283"
},
{
"fixed": "d3dcdb43c872a3b967345144151a2c9bb9124c9b"
},
{
"fixed": "22ae32d80ef590d12a2364e4621f90f7c58445c7"
},
{
"fixed": "7c1f23ad34fcdace50275a6aa1e1969b41c6233f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53658.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.9.0"
},
{
"fixed": "4.14.322"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.291"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.251"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.188"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.121"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.39"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.4.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53658.json"
}
}
],
"modified": "2026-10-30T02:30:45.694979033Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/217b6ea8cf7b819477bca597a6ae2d43d38ba283",
"https://git.kernel.org/stable/c/22ae32d80ef590d12a2364e4621f90f7c58445c7",
"https://git.kernel.org/stable/c/32b9c8f7892c19f7f5c9fed5fb410b9fd5990bb6",
"https://git.kernel.org/stable/c/398e6a015877d44327f754aeb48ff3354945c78c",
"https://git.kernel.org/stable/c/7c1f23ad34fcdace50275a6aa1e1969b41c6233f",
"https://git.kernel.org/stable/c/a91c34357afcfaa5307e254f22a8452550a07b34",
"https://git.kernel.org/stable/c/d20db3c58a7f9361e370a7850ceb60dbdf62eea3",
"https://git.kernel.org/stable/c/d3dcdb43c872a3b967345144151a2c9bb9124c9b",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53658.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53658",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53658.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53658",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 518685,
"published_at": "2025-10-07T15:21:18.95+00:00"
}