During kernel initialization the mtk_snand driver registers an on-host NAND ECC engine to accelerate error correction. The original code failed to unregister that engine when the probe returned an error or when the device was removed, leaving the ECC hardware reference allocated. The lingering reference can leave the hardware registers and kernel state in an uninitialized or inconsistent condition, which in turn could lead to system instability or a kernel crash if the same resources are later reused or overwritten. This flaw is strictly about missing cleanup; it does not expose a direct exploitation path, but the consequence is a denial of service through resource leakage.

The affected component is the Linux kernel for all builds that contain the mtk‑snfi SPI NAND driver. The specific affected kernel versions are not enumerated in the data, so any pre‑patch kernel that includes this driver is potentially impacted. Based on the description, it is inferred that any build containing the driver and lacking the new cleanup action is vulnerable.

The EPSS score is below 1 %, indicating a very low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Because the flaw involves kernel‑level resource management, it is likely to be noticed by an attacker with local or privileged access who can trigger or observe probe failures or device removal, potentially causing a kernel crash or denial of service. While no public exploit exists, the low EPSS score and lack of a remote exploitation vector suggest moderate overall risk, although the impact of a kernel crash warrants timely patching.