{"cve":"CVE-2026-98207","nvd":{"published":"2026-10-06T09:18:06.843","modified":"2026-10-19T10:18:21.373","status":"Received","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmmc: spi: reset bytes_xfered before retrying CRC failures\n\nmmc_spi_data_do() updates data->bytes_xfered after each block has been\ntransferred successfully.  If a later block in the same data request\nfails with a CRC error, data->bytes_xfered may therefore contain the\nnumber of bytes completed before the failing block.\n\nmmc_spi_request() has a private recovery path for such CRC failures.  It\nsends STOP_TRANSMISSION, clears data->error and jumps back to\ncrc_recover to issue the same command and data request again.  However,\nit does not clear data->bytes_xfered before the retry.\n\nIf the retry succeeds, the request is completed with the bytes from the\nfailed attempt still included in data->bytes_xfered.  For a multi-block\nrequest this can make the completed request report more bytes than were\ntransferred by the successful retry, and can even exceed the request size\nwhen most blocks completed before the CRC error.\n\nThis is most likely to be observed on MMC-over-SPI systems where long\nmulti-block transfers occasionally hit a data CRC error but the\nmmc_spi-internal retry succeeds.  The data itself is retried, but the\ncompletion accounting is not.\n\nClear data->bytes_xfered together with data->error before repeating the\nrequest so the final completion reports only the bytes transferred by the\nsuccessful attempt.","cvss_v4":null,"cvss_v3":null,"cwes":[],"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"],"products":[],"source":"nvd","synced_at":"2026-10-19T22:57:46.668721662+00:00"},"epss":{"cve":"CVE-2026-98207","score":0.00177,"percentile":0.07148,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}