Heimdall Security Logo

CVE-2026-98207

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <da4929ee78ee701c3717543840798fedff66c430, <=6.1.*, <=6.12.*, 2.6.37, <7d2f0ec16b300645f20435a6c3827b15e01419af, <2.6.37, 0, <8b0cc8707f65e0f51912e764e1b309b2559db1ec, <3ae80c1fb7de4d3331427a955a44807745ac5a33, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <57f5e29db63f7c80f1805d89234a74dcdbf60231, 7.2.8, <0b8c8504593409954ed1a60db4e437d814e04023, <=6.18.*, 5.15.222, <=7.2.*, 061c6c847eeb11743e489a16e907b41c6f9042b6, <4885e587f1afa9e1a573ab66f8c4d94d7b836d86, <=*, <=5.15.*, 6.18.54, <d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a, 7.3

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.

Gravité et risque d'exploitation

CVE-2026-98207 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 7.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <da4929ee78ee701c3717543840798fedff66c430, <=6.1.*, <=6.12.*, 2.6.37, <7d2f0ec16b300645f20435a6c3827b15e01419af, <2.6.37, 0, <8b0cc8707f65e0f51912e764e1b309b2559db1ec, <3ae80c1fb7de4d3331427a955a44807745ac5a33, 6.12.112, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, 6.1.189, <57f5e29db63f7c80f1805d89234a74dcdbf60231, 7.2.8, <0b8c8504593409954ed1a60db4e437d814e04023, <=6.18.*, 5.15.222, <=7.2.*, 061c6c847eeb11743e489a16e907b41c6f9042b6, <4885e587f1afa9e1a573ab66f8c4d94d7b836d86, <=*, <=5.15.*, 6.18.54, <d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE