CVE-2026-74373: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-w5h2-43j2-4p8f
Published
Advisory Summary

CVE-2026-74373 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-74373 at a Glance

CVE Identifier CVE-2026-74373
GHSA Identifier GHSA-w5h2-43j2-4p8f
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-74373

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-74373, 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: md/raid1,raid10: fix bio accounting for split md cloned bios Use md_cloned_bio() to control bio accounting instead of relying on r1bio_existed in raid1 or the io_accounting flag in raid10. The previous logic does not reliably reflect whether a bio is an md cloned bio. When a failed bio is split and resubmitted via bio_submit_split_bioset() on the error path, this can lead to either double accounting for md cloned bios, or missing accounting for bios returned from bio_submit_split_bioset() Fix this by using md_cloned_bio() to detect md cloned bios and skip accounting accordingly.

References

Frequently Asked Questions

What is CVE-2026-74373?
CVE-2026-74373 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-74373?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74373?
CVE-2026-74373 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74373?
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-w5h2-43j2-4p8f",
  "modified" : "2026-10-15T12:30:42Z",
  "published" : "2026-08-15T06:32:31Z",
  "aliases" : [ "CVE-2026-74373" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/raid1,raid10: fix bio accounting for split md cloned bios\n\nUse md_cloned_bio() to control bio accounting instead of relying\non r1bio_existed in raid1 or the io_accounting flag in raid10.\n\nThe previous logic does not reliably reflect whether a bio is an\nmd cloned bio. When a failed bio is split and resubmitted via\nbio_submit_split_bioset() on the error path, this can lead to either\ndouble accounting for md cloned bios, or missing accounting for bios\nreturned from bio_submit_split_bioset()\n\nFix this by using md_cloned_bio() to detect md cloned bios and\nskip accounting accordingly.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74373"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ba976e3501111d11c550848b3b7341a73035f582"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bb8d7ea74206b419aa05d7773a15a923b668c9f0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bcf30e14d2bd509c57e93021b46aedc878896e7b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:39Z"
  }
}