[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025010808-CVE-2024-56771-3ace@gregkh>
Date: Wed, 8 Jan 2025 18:49:09 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-56771: mtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information
These four chips:
* W25N512GW
* W25N01GW
* W25N01JW
* W25N02JW
all require a single bit of ECC strength and thus feature an on-die
Hamming-like ECC engine. There is no point in filling a ->get_status()
callback for them because the main ECC status bytes are located in
standard places, and retrieving the number of bitflips in case of
corrected chunk is both useless and unsupported (if there are bitflips,
then there is 1 at most, so no need to query the chip for that).
Without this change, a kernel warning triggers every time a bit flips.
The Linux kernel CVE team has assigned CVE-2024-56771 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit 6a804fb72de56d6a99b799f565ae45f2cec7cd55 and fixed in 6.12.4 with commit 234d5f75c3ae911b52c5e4442b8a87fbbd129836
Issue introduced in 6.7 with commit 6a804fb72de56d6a99b799f565ae45f2cec7cd55 and fixed in 6.13-rc1 with commit fee9b240916df82a8b07aef0fdfe96785417a164
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-2024-56771
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/nand/spi/winbond.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/234d5f75c3ae911b52c5e4442b8a87fbbd129836
https://git.kernel.org/stable/c/fee9b240916df82a8b07aef0fdfe96785417a164
Powered by blists - more mailing lists