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.
References
Configurations
Configuration 1 (hide)
|
History
19 Oct 2026, 19:17
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-362 |
15 Oct 2026, 02:18
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Information
Published : 2026-04-03 16:16
Updated : 2026-10-19 19:17
NVD link : CVE-2026-23434
Mitre link : CVE-2026-23434
CVE.ORG link : CVE-2026-23434
JSON object : View
Products Affected
linux
- linux_kernel
CWE
NVD-CWE-noinfo
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
