VulnerabilityPublished 19 Jul 2026

CVE-2026-63861: Linux kernel · spi: mtk-snfi: unregister ECC engine on probe failure and remove() callback

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-g8cm-gmx3-562c

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by adding automatic cleanup of the ECC engine on probe failure and device removal. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and apply updates accordingly.

Description

A vulnerability in the Linux kernel's MediaTek SNFI SPI driver (mtk-snfi) was resolved by ensuring proper cleanup of the NAND ECC engine on probe failure and device removal. The issue was that the ECC engine was registered during probe but not unregistered on failure or removal, potentially leading to resource leaks or inconsistent states. The fix adds a managed cleanup action to automatically unregister the ECC engine when probe fails or the device is removed.

Impact

The vulnerability could lead to improper resource management in the kernel driver, potentially causing system instability or unexpected behavior related to the NAND ECC engine. There is no indication of direct security compromise or exploitation in the wild.

Summary

The Linux kernel's mtk-snfi SPI driver had a flaw where the on-host NAND ECC engine was registered during the mtk_snand_probe() function but lacked corresponding teardown during probe failure or device removal. This could cause the ECC engine to remain registered improperly. The patch introduces a devm-managed cleanup action that calls nand_ecc_unregister_on_host_hw_engine() automatically on probe failure and device removal, ensuring proper resource management.

References

Community reviews

Loading reviews…