Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53658, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 95% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < a91c34357afcfaa5307e254f22a8452550a07b34
    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < d20db3c58a7f9361e370a7850ceb60dbdf62eea3
    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < 398e6a015877d44327f754aeb48ff3354945c78c
    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < 32b9c8f7892c19f7f5c9fed5fb410b9fd5990bb6
    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < 217b6ea8cf7b819477bca597a6ae2d43d38ba283
    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < d3dcdb43c872a3b967345144151a2c9bb9124c9b
    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < 22ae32d80ef590d12a2364e4621f90f7c58445c7
    • affected fa236a7ef24048bafaeed13f68df35a819794758 – < 7c1f23ad34fcdace50275a6aa1e1969b41c6233f
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 4.14.322 – ≤ 4.14.*
    • unaffected 4.19.291 – ≤ 4.19.*
    • unaffected 5.4.251 – ≤ 5.4.*
    • unaffected 5.10.188 – ≤ 5.10.*
    • unaffected 5.15.121 – ≤ 5.15.*
    • unaffected 6.1.39 – ≤ 6.1.*
    • unaffected 6.4.4 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53658 badge
[![CVE-2023-53658](https://cveledger.app/badge/CVE-2023-53658.svg)](https://cveledger.app/cve/CVE-2023-53658)

Record last updated .