GHSA-GX8R-25RX-RH7G
Vulnerability from github – Published: 2026-10-06 09:31 – Updated: 2026-10-06 09:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98207"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-06T09:18:06Z",
"severity": null
},
"details": "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-\u003ebytes_xfered after each block has been\ntransferred successfully. If a later block in the same data request\nfails with a CRC error, data-\u003ebytes_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-\u003eerror and jumps back to\ncrc_recover to issue the same command and data request again. However,\nit does not clear data-\u003ebytes_xfered before the retry.\n\nIf the retry succeeds, the request is completed with the bytes from the\nfailed attempt still included in data-\u003ebytes_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-\u003ebytes_xfered together with data-\u003eerror before repeating the\nrequest so the final completion reports only the bytes transferred by the\nsuccessful attempt.",
"id": "GHSA-gx8r-25rx-rh7g",
"modified": "2026-10-06T09:31:30Z",
"published": "2026-10-06T09:31:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98207"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0b8c8504593409954ed1a60db4e437d814e04023"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3ae80c1fb7de4d3331427a955a44807745ac5a33"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4885e587f1afa9e1a573ab66f8c4d94d7b836d86"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/57f5e29db63f7c80f1805d89234a74dcdbf60231"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7d2f0ec16b300645f20435a6c3827b15e01419af"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8b0cc8707f65e0f51912e764e1b309b2559db1ec"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/da4929ee78ee701c3717543840798fedff66c430"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.