Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98207mmc: spi: reset bytes_xfered before retrying CRC failures

Description

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. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < 7d2f0ec16b300645f20435a6c3827b15e01419af
    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a
    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < 0b8c8504593409954ed1a60db4e437d814e04023
    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < da4929ee78ee701c3717543840798fedff66c430
    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < 57f5e29db63f7c80f1805d89234a74dcdbf60231
    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < 4885e587f1afa9e1a573ab66f8c4d94d7b836d86
    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < 3ae80c1fb7de4d3331427a955a44807745ac5a33
    • affected 061c6c847eeb11743e489a16e907b41c6f9042b6 – < 8b0cc8707f65e0f51912e764e1b309b2559db1ec
  • Linux · Linux

    • affected 2.6.37
    • unaffected < 2.6.37
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98207 badge
[![CVE-2026-98207](https://cveledger.app/badge/CVE-2026-98207.svg)](https://cveledger.app/cve/CVE-2026-98207)

Record last updated .