[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025123030-CVE-2023-54295-8954@gregkh>
Date: Tue, 30 Dec 2025 13:23:48 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54295: mtd: spi-nor: Fix shift-out-of-bounds in spi_nor_set_erase_type
From: Greg Kroah-Hartman <gregkh@...nel.org>
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]
The Linux kernel CVE team has assigned CVE-2023-54295 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.20 with commit 5390a8df769ec9ba9c995191bb0867430f602ebb and fixed in 5.10.173 with commit e6409208c13f7c56adc12dd795abf4141e3d5e64
Issue introduced in 4.20 with commit 5390a8df769ec9ba9c995191bb0867430f602ebb and fixed in 5.15.99 with commit 61d44a4db2f54dbac7d22c2541574ea5755e0468
Issue introduced in 4.20 with commit 5390a8df769ec9ba9c995191bb0867430f602ebb and fixed in 6.1.16 with commit 53b2916ebde741c657a857fa1936c0d9fcb59170
Issue introduced in 4.20 with commit 5390a8df769ec9ba9c995191bb0867430f602ebb and fixed in 6.2.3 with commit 99341b8aee7b5b4255b339345bbcaa35867dfd0c
Issue introduced in 4.20 with commit 5390a8df769ec9ba9c995191bb0867430f602ebb and fixed in 6.3 with commit f0f0cfdc3a024e21161714f2e05f0df3b84d42ad
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-54295
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/mtd/spi-nor/core.c
drivers/mtd/spi-nor/core.h
drivers/mtd/spi-nor/sfdp.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e6409208c13f7c56adc12dd795abf4141e3d5e64
https://git.kernel.org/stable/c/61d44a4db2f54dbac7d22c2541574ea5755e0468
https://git.kernel.org/stable/c/53b2916ebde741c657a857fa1936c0d9fcb59170
https://git.kernel.org/stable/c/99341b8aee7b5b4255b339345bbcaa35867dfd0c
https://git.kernel.org/stable/c/f0f0cfdc3a024e21161714f2e05f0df3b84d42ad
Powered by blists - more mailing lists