Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-98207

mmc: spi: reset bytes_xfered before retrying CRC failures

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
None on Exploit-DB, Metasploit or GitHub

Summary

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.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in 7d2f0ec16b300645f20435a6c3827b15e01419af; From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a; From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in 0b8c8504593409954ed1a60db4e437d814e04023; From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in da4929ee78ee701c3717543840798fedff66c430; From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in 57f5e29db63f7c80f1805d89234a74dcdbf60231; From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in 4885e587f1afa9e1a573ab66f8c4d94d7b836d86; From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in 3ae80c1fb7de4d3331427a955a44807745ac5a33; From 061c6c847eeb11743e489a16e907b41c6f9042b6 · fixed in 8b0cc8707f65e0f51912e764e1b309b2559db1ec

  • Linux Linux

    2.6.37

  • KernelLinux

    From 2.6.37 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8

References 8

git.kernel.org