mtd: rawnand: serialize lock/unlock against other NAND operations
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux 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 Linux
5.7
- KernelLinux
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
References 8
git.kernel.org
- stable/c/28ea836cc44cb8b89c1c174707ead0c1133c60e9
- stable/c/fe4a73c3dd48308149d57a10c2761e1d36ced7ba
- stable/c/ce5229e78078e437704157eb542f43a6f83b429b
- stable/c/a80291e577b44593a724d6cd64c14337c78f194d
- stable/c/f71ce0ae5aefe39dd5b2f996c0e08550d2153ad2
- stable/c/5fd5c078af23cb353507aa522e09d557d7eaef04
- stable/c/f25446e2c28939753d3b62d34dfda49952b2557d
- stable/c/bab2bc6e850a697a23b9e5f0e21bb8c187615e95