
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-23434 is a race condition vulnerability in the Linux kernel's MTD raw NAND driver affecting the nand_lock() and nand_unlock() functions. These functions invoke chip->ops.lock_area/unlock_area without holding the NAND device lock, enabling races with concurrent UBI/UBIFS background erase/write operations on controllers that implement SET_FEATURES via multiple low-level PIO commands. Affected kernel versions span 5.7 through numerous stable branches up to 6.19.9 and 7.0-rc1 through 7.0-rc7. It was published on April 3, 2026, and carries a CVSS v3.1 base score of 5.5 (Medium) (GitHub Advisory, Feedly).
The root cause is a concurrency control flaw (CWE-362: Race Condition) in the Linux kernel's drivers/mtd/nand/raw/ subsystem. nand_lock() and nand_unlock() call into chip-level lock/unlock area operations without first acquiring the NAND device lock via nand_get_device()/nand_release_device(). On NAND controllers that implement SET_FEATURES through sequences of multiple low-level PIO commands, a concurrent UBI/UBIFS background erase or write operation — which does hold the device lock — can interleave with these sequences, producing cmd_pending conflicts on the controller. The fix wraps the lock/unlock operations with nand_get_device()/nand_release_device() to serialize all NAND controller access (GitHub Advisory, Feedly).
Successful exploitation can result in cmd_pending conflicts on the NAND controller, leading to data corruption or system instability on affected devices. The vulnerability has no confidentiality or integrity impact in the traditional sense but poses a high availability risk, as conflicting concurrent NAND operations can render flash storage unreliable or cause kernel-level errors. Systems most at risk are those running embedded or industrial Linux environments with NAND flash storage and active UBI/UBIFS workloads performing frequent background erase/write cycles (Feedly).
Apply the upstream kernel patches available across multiple stable branches. Patched versions include: 5.10.253+, 5.15.203+, 6.1.167+, 6.6.130+, 6.12.78+, 6.18.20+, and 6.19.10+; the fix is also included in 7.0 stable releases. Distribution-specific updates have been issued by SUSE (SUSE-SU-2026:2217-1, SUSE-SU-2026:2238-1), Debian (linux 5.10.257-1 for oldoldstable-security), and openSUSE. As a workaround where patching is not immediately possible, avoid concurrent NAND lock/unlock operations alongside active UBI/UBIFS background tasks, though upgrading to a patched kernel is the only definitive remediation (GitHub Advisory, SUSE Advisory, Debian Tracker).
The vulnerability was announced via the official Linux kernel CVE mailing list and tracked by multiple distribution security teams including SUSE, Debian, and the Yocto Project. Tenable published detection plugins (Nessus plugin 304958 and 318288) for the vulnerability. No notable independent researcher commentary or significant social media discussion has been observed beyond routine patch tracking (Yocto Security, Tenable).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."