Impact
In the Linux kernel, the SLRAM MTD device registration routine links a new list entry before allocating all of the state needed by that entry. If a later allocation, memremap(), or mtd_device_register() fails, the partially initialized entry remains on the global list. When the system later performs cleanup, that dangling entry causes the kernel to dereference or free invalid memory, resulting in kernel memory corruption that can lead to a panic or loss of service. Based on the description, it is inferred that an attacker able to trigger the failure path—such as by supplying malformed device registration data—could potentially exploit this flaw to gain elevated privileges or disrupt kernel operation.
Affected Systems
All Linux kernel builds that include the SLRAM MTD subsystem are affected. No specific upstream version numbers are provided; any kernel without the corresponding fix will be vulnerable.
Risk and Exploitability
The CVSS score of 7.8 indicates a high severity, while the EPSS score of < 1% demonstrates a low probability of exploitation. The flaw is not listed in the CISA KEV catalog. The likely attack vector is local, requiring an attacker to influence device registration or trigger a failure during MTD cleanup. Although no public exploits are documented, the combination of kernel memory corruption and the possibility of privilege escalation renders the risk significant for affected systems.
OpenCVE Enrichment