Live › vulnerability › CVE-2026-98834
Go to dashboardWhen factory OTP setup fails in the MTD subsystem, the user OTP NVMEM device is unregistered but its pointer is left set, so it can be unregistered a second time. The sources describe a double-free, but do not state what an attacker gains from it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
mtd: core: avoid double-free of OTP NVMEM device
If factory OTP setup fails after the user OTP NVMEM device has been registered, mtd_otp_nvmem_add() unregisters the user device but leaves mtd->otp_user_nvmem set. On an error, the caller unregisters it again. For -EOPNOTSUPP, registration continues and normal teardown unregisters it again.
Clear mtd->otp_user_nvmem after unregistering it.
This page as .md · .json · in your agent: get_signal("CVE-2026-98834")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.