CVE-2026-98207: Linux kernel · mmc: spi: reset bytes_xfered before retrying CRC failures
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:27 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: mmc: spi: reset bytes_xfered before retrying CRC failures mmc_spi_data_do() updates data->bytes_xfered after each block has been transferred successfully. If a later block in the same data request fails with a CRC error, data->bytes_xfered may therefore contain the number of bytes completed before the failing block. mmc_spi_request() has a private recovery path for such CRC failures. It sends STOP_TRANSMISSION, clears data->error and jumps back to crc_recover to issue the same command and data request again. However, it does not clear data->bytes_xfered before the retry. If the retry succeeds, the request is completed with the bytes from the failed attempt still included in data->bytes_xfered. For a multi-block request this can make the completed request report more bytes than were transferred by the successful retry, and can even exceed the request size when most blocks completed before the CRC error. This is most likely to be observed on MMC-over-SPI systems where long multi-block transfers occasionally hit a data CRC error but the mmc_spi-internal retry succeeds. The data itself is retried, but the completion accounting is not. Clear data->bytes_xfered together with data->error before repeating the request so the final completion reports only the bytes transferred by the successful attempt.
References
- ubuntu.com/security/CVE-2026-98207 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98207 (opens in a new tab)
- git.kernel.org/linus/8b0cc8707f65e0f51912e764e1b309b2559db1ec (opens in a new tab)
- git.kernel.org/stable/c/0b8c8504593409954ed1a60db4e437d814e04023 (opens in a new tab)
- git.kernel.org/stable/c/3ae80c1fb7de4d3331427a955a44807745ac5a33 (opens in a new tab)
- git.kernel.org/stable/c/4885e587f1afa9e1a573ab66f8c4d94d7b836d86 (opens in a new tab)
- git.kernel.org/stable/c/57f5e29db63f7c80f1805d89234a74dcdbf60231 (opens in a new tab)
- git.kernel.org/stable/c/7d2f0ec16b300645f20435a6c3827b15e01419af (opens in a new tab)
- git.kernel.org/stable/c/8b0cc8707f65e0f51912e764e1b309b2559db1ec (opens in a new tab)
- git.kernel.org/stable/c/d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a (opens in a new tab)
- git.kernel.org/stable/c/da4929ee78ee701c3717543840798fedff66c430 (opens in a new tab)