CVE-2026-98207: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-gx8r-25rx-rh7g
Published
Advisory Summary

CVE-2026-98207 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98207 at a Glance

CVE Identifier CVE-2026-98207
GHSA Identifier GHSA-gx8r-25rx-rh7g
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98207

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98207, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

Frequently Asked Questions

What is CVE-2026-98207?
CVE-2026-98207 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98207?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98207?
CVE-2026-98207 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98207?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gx8r-25rx-rh7g",
  "modified" : "2026-10-06T09:31:30Z",
  "published" : "2026-10-06T09:31:30Z",
  "aliases" : [ "CVE-2026-98207" ],
  "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->bytes_xfered after each block has been\ntransferred successfully.  If a later block in the same data request\nfails with a CRC error, data->bytes_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->error and jumps back to\ncrc_recover to issue the same command and data request again.  However,\nit does not clear data->bytes_xfered before the retry.\n\nIf the retry succeeds, the request is completed with the bytes from the\nfailed attempt still included in data->bytes_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->bytes_xfered together with data->error before repeating the\nrequest so the final completion reports only the bytes transferred by the\nsuccessful attempt.",
  "severity" : [ ],
  "affected" : [ ],
  "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"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-06T09:18:06Z"
  }
}