mtd: rawnand: serialize lock/unlock against other NAND operations
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 92270086b7e5ada7ab381c06cc3da2e95ed17088 · < 5fd5c078af23cb353507aa522e09d557d7eaef04| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mtd: rawnand: serialize lock/unlock against other NAND operations
nand_lock() and nand_unlock() call into chip->ops.lock_area/unlock_area without holding the NAND device lock. On controllers that implement SET_FEATURES via multiple low-level PIO commands, these can race with concurrent UBI/UBIFS background erase/write operations that hold the device lock, resulting in cmd_pending conflicts on the NAND controller.
Add nand_get_device()/nand_release_device() around the lock/unlock operations to serialize them against all other NAND controller access.
From the CVE record · Linux
Linux kernel raw NAND lock and unlock operations do not hold the NAND device lock. On controllers that implement SET_FEATURES through multiple low-level PIO commands, they can race with concurrent UBI/UBIFS erase or write operations, causing NAND controller command conflicts. The input does not specify an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernel systems with raw NAND controllers should check their kernel versions; affected versions are not specified.