High · published April 3, 2026
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.
| Product | Versions | Fixed in |
|---|---|---|
| linux/linux_kernel | ≥ 5.7.1, < 5.10.253 | 5.10.253 |
| linux/linux_kernel | ≥ 5.11, < 5.15.203 | 5.15.203 |
| linux/linux_kernel | ≥ 5.16, < 6.1.167 | 6.1.167 |
| linux/linux_kernel | ≥ 6.2, < 6.6.130 | 6.6.130 |
| linux/linux_kernel | ≥ 6.7, < 6.12.78 | 6.12.78 |
| linux/linux_kernel | ≥ 6.13, < 6.18.20 | 6.18.20 |
| linux/linux_kernel | ≥ 6.19, < 6.19.10 | 6.19.10 |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |