CVE-2026-98207

Source
https://cve.org/CVERecord?id=CVE-2026-98207
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98207.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-98207
Downstream
Published
2026-10-06T08:44:44Z
Modified
2026-10-08T02:52:53Z
Summary
mmc: spi: reset bytes_xfered before retrying CRC failures
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98207.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.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"

Linux / Kernel

Package

Name
Kernel

Affected 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

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98207.json"