CVE-2026-124017 in E12
Summary
by MITRE • 11/16/2026
Phison E12 and E18 PCIe SSD controllers contain a Secure Boot bypass vulnerability that allows a privileged local attacker to inject persistent boot-patch tuples into the unsigned, CRC-protected flash ID page read by the BootROM. By overwriting a fuse-derived RAM variable via a crafted patch entry using Phison Vendor Specific Commands, an attacker can force CRC-only firmware verification instead of signature checking, enabling an unsigned firmware image to load and creating a persistent controller-level implant that survives firmware reinstallation and operates below the host operating system.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 11/16/2026
The vulnerability identified in Phison E12 and E18 PCIe SSD controllers represents a critical failure in the hardware-based Secure Boot chain, specifically targeting the interaction between the BootROM and the flash memory ID page. This flaw allows for a sophisticated bypass of firmware integrity checks by exploiting how the controller validates its own boot code. The core technical issue lies in the handling of the unsigned, CRC-protected flash ID page during the initial boot sequence. An attacker with local privileged access can leverage Phison Vendor Specific Commands to manipulate internal state variables derived from hardware fuses. By injecting crafted patch entries into this specific memory region, the attacker forces the BootROM to rely solely on Cyclic Redundancy Check verification rather than requiring a valid cryptographic signature. This substitution effectively neutralizes the primary defense mechanism designed to prevent unauthorized code execution at the lowest levels of storage controller firmware.
From an operational perspective, this vulnerability enables the creation of a persistent implant that resides within the SSD's internal memory and operates below the host operating system. Because the malicious patch is stored in the flash ID page or associated volatile RAM structures that are preserved across reboots and even firmware updates, traditional remediation methods such as flashing new firmware do not remove the threat. The attacker gains a foothold that persists independently of the OS environment, allowing for long-term surveillance, data exfiltration, or further lateral movement within a network infrastructure. This level of persistence is particularly dangerous because it bypasses standard endpoint detection and response tools that typically focus on software-level anomalies rather than hardware firmware manipulation.
The security implications align closely with CWE-287, which describes Improper Authentication, as the controller fails to properly verify the authenticity of its own boot image before execution. Furthermore, this attack vector maps directly to MITRE ATT&CK technique T1505.003, known as Server Software Component: Storage Module, where adversaries install a persistent component within storage hardware to maintain access and evade detection. The ability to bypass signature checks in favor of simple checksum validation represents a fundamental breakdown in the trust model established by Secure Boot implementations for enterprise storage devices.
Mitigation strategies must address both immediate remediation and long-term architectural changes. Currently, there may be no direct software patch available that can remove this implant once installed due to its persistence in low-level controller memory. Therefore, physical replacement of affected SSDs is often the only reliable method to fully eradicate the threat if an attack has already occurred. For prevention, Phison and system manufacturers must enforce stricter validation processes for Vendor Specific Commands and ensure that fuse-derived variables cannot be overwritten by user-space or privileged applications without additional cryptographic verification. Future firmware designs should implement immutable storage regions for critical boot parameters and require multi-factor authentication at the hardware level to prevent unauthorized modification of the flash ID page during runtime operations.