In the Linux kernel, a race condition occurs when nand_lock() and nand_unlock() are executed without holding the NAND device lock. This allows concurrent UBI/UBIFS background operations to overlap with SET_FEATURES commands that use multiple PIO operations, producing cmd_pending conflicts that can corrupt NAND transactions or cause system instability. The flaw is a concurrency weakness (CWE‑362) that may compromise data integrity.

The vulnerability affects all Linux kernel builds that include the MTD raw NAND subsystem on controllers that use multi‑PIO SET_FEATURES, especially those operating UBI/UBIFS file systems. No specific kernel version is listed, so any release before the patch that adds nand_get_device()/nand_release_device() around lock/unlock is considered vulnerable.

No CVSS or EPSS data is available and the flaw is not in CISA's KEV catalog. Exploitation would require precursor kernel‑level access to trigger concurrent NAND operations, meaning an attacker would need to run privileged software or firmware. The potential impact is data corruption or denial of service, but the attack vector is limited to high‑permission context rather than external exploitation.