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

Published Apr 3, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mtd: rawnand: serialize lock/unlock against other NAND operations

nandlock() and nandunlock() call into chip->ops.lockarea/unlockarea without holding the NAND device lock. On controllers that implement SETFEATURES via multiple low-level PIO commands, these can race with concurrent UBI/UBIFS background erase/write operations that hold the device lock, resulting in cmdpending conflicts on the NAND controller.

Add nandgetdevice()/nandreleasedevice() around the lock/unlock operations to serialize them against all other NAND controller access.

Affected Software

17 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.7.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.167
Linux Linux kernel>=6.2<6.6.130
Linux Linux kernel>=6.7<6.12.78
Linux Linux kernel>=6.13<6.18.20
Linux Linux kernel>=6.19<6.19.10
Linux Linux kernel=5.7
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Compensating control

    In the Linux kernel mtd: rawnand implementation, call nand_get_device() before nand_lock()/nand_unlock() invoke chip->ops.lock_area/unlock_area, and call nand_release_device() afterward to serialize these operations against other NAND controller access.

Event History

Apr 3, 2026
CVE Published
via MITRE·03:15 PM
Data Sourced
via MITRE·03:15 PM
DescriptionSeverity
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 25, 2026
Data Sourced
via Microsoft·08:05 AM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-23434?

The severity of CVE-2026-23434 is high with a score of 7.1.

2

How do I fix CVE-2026-23434?

To fix CVE-2026-23434, you should update the Linux kernel to the latest patched version that addresses this vulnerability.

3

What impact does CVE-2026-23434 have on Linux systems?

CVE-2026-23434 can lead to potential data corruption or denial of service on systems using vulnerable NAND flash devices.

4

Which versions of the Linux kernel are affected by CVE-2026-23434?

CVE-2026-23434 affects specific versions of the Linux kernel prior to the release of the patch that addresses this vulnerability.

5

Is CVE-2026-23434 exploitable remotely?

CVE-2026-23434 has a low attack vector rating, making remote exploitation less likely but still possible under certain conditions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203