CVE-2026-23434
Medium
Elevated severity or exploit probability.
CVSS base
7.1
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS — probability of exploitation (30 days)
0.1%
3.2th percentile
CISA KEV
Not listed
Weakness / dates
—
Published 2026-04-03 · modified 2026-07-24
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | N | None |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2026-04-03 — Published (NVD)
- 2026-07-24 — Last modified (NVD)
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.
Affected
References
- https://git.kernel.org/stable/c/28ea836cc44cb8b89c1c174707ead0c1133c60e9
- https://git.kernel.org/stable/c/5fd5c078af23cb353507aa522e09d557d7eaef04
- https://git.kernel.org/stable/c/a80291e577b44593a724d6cd64c14337c78f194d
- https://git.kernel.org/stable/c/bab2bc6e850a697a23b9e5f0e21bb8c187615e95
- https://git.kernel.org/stable/c/ce5229e78078e437704157eb542f43a6f83b429b
- https://git.kernel.org/stable/c/f25446e2c28939753d3b62d34dfda49952b2557d
- https://git.kernel.org/stable/c/f71ce0ae5aefe39dd5b2f996c0e08550d2153ad2
- https://git.kernel.org/stable/c/fe4a73c3dd48308149d57a10c2761e1d36ced7ba
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html