Skip to main content

Linux CVE-2026-98207

| EUVDEUVD-2026-93135
2026-10-06 Linux GHSA-gx8r-25rx-rh7g
View
Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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.

Affected VersionsENISA

Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <3ae80c1fb7de4d3331427a955a44807745ac5a33
Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <4885e587f1afa9e1a573ab66f8c4d94d7b836d86
Linux patch: 6.18.54
Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <57f5e29db63f7c80f1805d89234a74dcdbf60231
Linux patch: 6.1.189
Linux 2.6.37
Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <d1acf4b9f6e9697406ce84ee9acfb92e094d5c7a
Linux patch: 7.2.8
Linux patch: 7.3-rc4
Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <8b0cc8707f65e0f51912e764e1b309b2559db1ec
Linux patch: 6.6.158
Linux patch: 5.15.222
Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <0b8c8504593409954ed1a60db4e437d814e04023
Linux patch: 0
Linux patch: 6.12.112
Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <7d2f0ec16b300645f20435a6c3827b15e01419af
Linux patch: 5.10.271
Linux 061c6c847eeb11743e489a16e907b41c6f9042b6 <da4929ee78ee701c3717543840798fedff66c430

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Oct 06, 2026 - 10:02 EUVD
CVE Published
Oct 06, 2026 - 08:44 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Threat Intel
1
1 sources
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy