Skip to content
Heist/ feed
Back to feed
UnratedFix available

mmc: spi: reset bytes_xfered before retrying CRC failures

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.10.271, 5.15.222, 6.1.189, 6.12.112, 6.18.54, 6.6.158, 7.2.8
CVEs
CVE-2026-98207
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 16:29 UTC · Revision 1

Source evidence

mmc: spi: reset bytes_xfered before retrying CRC failures

core-osv · Original source

Published 6 Oct 2026, 08:44 UTC

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.

osv:CVE-2026-98207

Kernel

Fixed versions: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8

Complete source record
{
  "id": "d81ca86213158bb07daa94625fd23759996be72eba1f14bbc76b9af693fc9a48",
  "url": "https://osv.dev/vulnerability/CVE-2026-98207",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "mmc: spi: reset bytes_xfered before retrying CRC failures",
    "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.",
    "evidence": "osv:CVE-2026-98207",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.10.271",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.222",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.189",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.158",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.112",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.54",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.2.8",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-98207",
      "aliases": [
        "CVE-2026-98207"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "061c6c847eeb11743e489a16e907b41c6f9042b6"
                },
                {
                  "fixed": "7d2f0ec16b300645f20435a6c3827b15e01419af"
                },
                {
                  "fixed": "d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a"
                },
                {
                  "fixed": "0b8c8504593409954ed1a60db4e437d814e04023"
                },
                {
                  "fixed": "da4929ee78ee701c3717543840798fedff66c430"
                },
                {
                  "fixed": "57f5e29db63f7c80f1805d89234a74dcdbf60231"
                },
                {
                  "fixed": "4885e587f1afa9e1a573ab66f8c4d94d7b836d86"
                },
                {
                  "fixed": "3ae80c1fb7de4d3331427a955a44807745ac5a33"
                },
                {
                  "fixed": "8b0cc8707f65e0f51912e764e1b309b2559db1ec"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98207.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "2.6.37"
                },
                {
                  "fixed": "5.10.271"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.222"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "6.1.189"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.158"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.112"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.54"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.2.8"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98207.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:30.461481384Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/0b8c8504593409954ed1a60db4e437d814e04023",
        "https://git.kernel.org/stable/c/3ae80c1fb7de4d3331427a955a44807745ac5a33",
        "https://git.kernel.org/stable/c/4885e587f1afa9e1a573ab66f8c4d94d7b836d86",
        "https://git.kernel.org/stable/c/57f5e29db63f7c80f1805d89234a74dcdbf60231",
        "https://git.kernel.org/stable/c/7d2f0ec16b300645f20435a6c3827b15e01419af",
        "https://git.kernel.org/stable/c/8b0cc8707f65e0f51912e764e1b309b2559db1ec",
        "https://git.kernel.org/stable/c/d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a",
        "https://git.kernel.org/stable/c/da4929ee78ee701c3717543840798fedff66c430",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98207.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-98207",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98207.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-98207",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 497373,
  "published_at": "2026-10-06T08:44:44.241+00:00"
}