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-54295mtd: spi-nor: Fix shift-out-of-bounds in spi_nor_set_erase_type

Description

In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: Fix shift-out-of-bounds in spi_nor_set_erase_type spi_nor_set_erase_type() was used either to set or to mask out an erase type. When we used it to mask out an erase type a shift-out-of-bounds was hit: UBSAN: shift-out-of-bounds in drivers/mtd/spi-nor/core.c:2237:24 shift exponent 4294967295 is too large for 32-bit type 'int' The setting of the size_{shift, mask} and of the opcode are unnecessary when the erase size is zero, as throughout the code just the erase size is considered to determine whether an erase type is supported or not. Setting the opcode to 0xFF was wrong too as nobody guarantees that 0xFF is an unused opcode. Thus when masking out an erase type, just set the erase size to zero. This will fix the shift-out-of-bounds. [ta: refine changes, new commit message, fix compilation error]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 5390a8df769ec9ba9c995191bb0867430f602ebb – < e6409208c13f7c56adc12dd795abf4141e3d5e64
    • affected 5390a8df769ec9ba9c995191bb0867430f602ebb – < 61d44a4db2f54dbac7d22c2541574ea5755e0468
    • affected 5390a8df769ec9ba9c995191bb0867430f602ebb – < 53b2916ebde741c657a857fa1936c0d9fcb59170
    • affected 5390a8df769ec9ba9c995191bb0867430f602ebb – < 99341b8aee7b5b4255b339345bbcaa35867dfd0c
    • affected 5390a8df769ec9ba9c995191bb0867430f602ebb – < f0f0cfdc3a024e21161714f2e05f0df3b84d42ad
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.99 – ≤ 5.15.*
    • unaffected 6.1.16 – ≤ 6.1.*
    • unaffected 6.2.3 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .