Linux kernel denial of service in SPI-NAND probe without ECC
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f9d7c7265bcff7d9a17425a8cddf702e8fe159c2 · < b890e6163761ddb580cc74f43e15f8bbde15647e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mtd: spinand: fix NULL pointer dereference with no ECC engine
When "nand-no-ecc-engine" is set in DT, nanddev_get_ecc_engine() takes the NAND_ECC_ENGINE_TYPE_NONE path and returns success while leaving nand->ecc.engine NULL. The SPI-NAND code nevertheless dereferences it unconditionally to test for a pipelined engine, so probing such a device oopses immediately.
Rather than open-coding the test three times, add a nand_ecc_is_pipelined() helper to the NAND core that folds the NULL check into the integration comparison, and use it everywhere. Future callers then cannot reintroduce the problem.
From the CVE record · Linux
The Linux kernel’s SPI-NAND code dereferences a NULL ECC engine while probing a device whose device tree sets `nand-no-ecc-engine`. This immediately crashes the kernel during probing; the input does not describe an attacker-controlled trigger or authentication requirements.
Engineers running Linux kernels with SPI-NAND devices configured with `nand-no-ecc-engine` should check their systems; affected versions are not specified.