Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 0b8c8504593409954ed1a60db4e437d814e04023, 3ae80c1fb7de4d3331427a955a44807745ac5a33, 4885e587f1afa9e1a573ab66f8c4d94d7b836d86; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.

Low priority for now. Upgrade to Linux Linux 0b8c8504593409954ed1a60db4e437d814e04023, 3ae80c1fb7de4d3331427a955a44807745ac5a33, 4885e587f1afa9e1a573ab66f8c4d94d7b836d86; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 6, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98207

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.37affected
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before 7d2f0ec16b300645f20435a6c3827b15e01419afaffected · git
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before d1acf4b9f6e9697406ce84ee9acfb92e094d5c7aaffected · git
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before 0b8c8504593409954ed1a60db4e437d814e04023affected · git
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before da4929ee78ee701c3717543840798fedff66c430affected · git
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before 57f5e29db63f7c80f1805d89234a74dcdbf60231affected · git
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before 4885e587f1afa9e1a573ab66f8c4d94d7b836d86affected · git
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before 3ae80c1fb7de4d3331427a955a44807745ac5a33affected · git
    • 061c6c847eeb11743e489a16e907b41c6f9042b6 and later · before 8b0cc8707f65e0f51912e764e1b309b2559db1ecaffected · git
    • before 2.6.37not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.8-17.2.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98205Oct 6, 2026 · Input: evdev - zero absinfo before partial copy in EVIOCSABS
    0Monitor
  • ← EarlierCVE-2026-98206Oct 6, 2026 · Input: cyttsp5 - clamp the HID report size before memcpy
    0Monitor
  • Later →CVE-2026-98208Oct 6, 2026 · mmc: sdio_uart: fix xmit_fifo leak when the port table is full
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0b8c8504593409954ed1a60db4e437d814e04023Vendor (CNA)
Linux Linux3ae80c1fb7de4d3331427a955a44807745ac5a33Vendor (CNA)
Linux Linux4885e587f1afa9e1a573ab66f8c4d94d7b836d86Vendor (CNA)
Linux Linux57f5e29db63f7c80f1805d89234a74dcdbf60231Vendor (CNA)
Linux Linux7d2f0ec16b300645f20435a6c3827b15e01419afVendor (CNA)
Linux Linux8b0cc8707f65e0f51912e764e1b309b2559db1ecVendor (CNA)
Linux Linuxd1acf4b9f6e9697406ce84ee9acfb92e094d5c7aVendor (CNA)
Linux Linuxda4929ee78ee701c3717543840798fedff66c430Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayOct 30, 2026+24 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records