CVE-2023-54295

mtd: spi-nor: Fix shift-out-of-bounds in spi_nor_set_erase_type

N/A
Published: December 30, 2025 at 12:23 PM UTC
Updated: June 17, 2026 at 06:47 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.20 ≤ v < 5.10.1734.20 ≤ v < 5.15.994.20 ≤ v < 6.1.164.20 ≤ v < 6.2.34.20 ≤ v < 6.34.205390a8df769ec9ba9c995191bb0867430f602ebb
Vendor states this is fixed in 53b2916ebde741c657a857fa1936c0d9fcb59170 (fixed)
Vendor states this is fixed in 61d44a4db2f54dbac7d22c2541574ea5755e0468 (fixed)
Vendor states this is fixed in 99341b8aee7b5b4255b339345bbcaa35867dfd0c (fixed)
Vendor states this is fixed in e6409208c13f7c56adc12dd795abf4141e3d5e64 (fixed)
Vendor states this is fixed in f0f0cfdc3a024e21161714f2e05f0df3b84d42ad (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.173 (unaffected)
Vendor states this is fixed in 5.15.99 (unaffected)
Vendor states this is fixed in 6.1.16 (unaffected)
Vendor states this is fixed in 6.2.3 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card