mtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel mishandles ECC status information for four Winbond SPI NAND chips, triggering a kernel warning whenever a bit flips. The input does not describe an attacker action or specify network access, authentication, or user-interaction conditions.
Engineers running Linux kernels with W25N512GW, W25N01GW, W25N01JW, or W25N02JW chips should check whether their kernel includes the fix; affected versions are not specified.