CVE-2026-98071: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-7v4m-g362-6xhw
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98071
GHSA Identifier GHSA-7v4m-g362-6xhw
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-98071

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-98071, 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: net/rds: clear cp_flags bits individually in rds_conn_path_reset() rds_conn_path_reset() wipes the whole flag word with a plain cp->cp_flags = 0 store. Every other accessor of that word uses atomic bitops, and some of them can run concurrently with the reset: RDS_LL_SEND_FULL is set from rds_send_xmit() and cleared from the transport completion paths, neither of which holds anything that excludes the shutdown worker. A plain store racing an atomic read-modify-write on the same word is a data race, and whichever side loses has its update silently discarded. Clear the two bits the reset is actually responsible for instead. RDS_IN_XMIT and RDS_RECV_REFILL need no store at all here: they belong to the caller, rds_conn_shutdown(), which waits for both to be clear before calling the transport shutdown and this reset. This also gives every bit in cp_flags a single well-defined writer discipline, which the following patches rely on when they turn RDS_IN_XMIT and RDS_RECV_REFILL into bit locks held across the teardown: a blanket store mid-teardown would destroy lock ownership that an atomic clear preserves. Oracle UEK carries the same conversion ("net/rds: Preserve essential connection state flags"), motivated by its asynchronous shutdown state machine, whose progress and destroy flags must survive the reset. UEK's variant also clears RDS_IN_XMIT and RDS_RECV_REFILL because there the reset runs as the final step of a teardown that owns both bits, making those clears its unlock. Upstream that release belongs in rds_conn_shutdown(): once a later patch in this series turns the two bits into locks held across the teardown, ending ownership needs release semantics and a wake-up that a plain clear inside the reset would not provide. Based on Oracle UEK commit "net/rds: Preserve essential connection state flags" by Gerd Rausch.

References

NVD — CVE-2026-98071 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98071
git.kernel.org/stable/c/103c4b13c4... WEB
https://git.kernel.org/stable/c/103c4b13c4f50322910078d1c02f29334a574122
git.kernel.org/stable/c/6b8d7563c2... WEB
https://git.kernel.org/stable/c/6b8d7563c28b8112e6e54abe413b028ef3f8c549
git.kernel.org/stable/c/b767b48614... WEB
https://git.kernel.org/stable/c/b767b48614c38687d717082860de7aa46f3b142c
git.kernel.org/stable/c/b7dc5da660... WEB
https://git.kernel.org/stable/c/b7dc5da660eb5ffa7f7b4d33f2c74cb71c6edd6c
git.kernel.org/stable/c/b8a8b6d25e... WEB
https://git.kernel.org/stable/c/b8a8b6d25e7426a638c60eaba2129c0664131e84
git.kernel.org/stable/c/c9a7c1eb0a... WEB
https://git.kernel.org/stable/c/c9a7c1eb0ad41dcf004a9e870e452cafedcd9172
git.kernel.org/stable/c/cb62aa8f04... WEB
https://git.kernel.org/stable/c/cb62aa8f04655a4df487913949719c0a1266ed73
git.kernel.org/stable/c/ed3ee0ac4a... WEB
https://git.kernel.org/stable/c/ed3ee0ac4aafda50c2f4381eb973beefeb7879ac

Frequently Asked Questions

What is CVE-2026-98071?
CVE-2026-98071 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-98071?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98071?
CVE-2026-98071 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98071?
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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7v4m-g362-6xhw",
  "modified" : "2026-10-03T12:31:26Z",
  "published" : "2026-09-25T12:31:35Z",
  "aliases" : [ "CVE-2026-98071" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/rds: clear cp_flags bits individually in rds_conn_path_reset()\n\nrds_conn_path_reset() wipes the whole flag word with a plain\ncp->cp_flags = 0 store.  Every other accessor of that word uses\natomic bitops, and some of them can run concurrently with the reset:\nRDS_LL_SEND_FULL is set from rds_send_xmit() and cleared from the\ntransport completion paths, neither of which holds anything that\nexcludes the shutdown worker.  A plain store racing an atomic\nread-modify-write on the same word is a data race, and whichever\nside loses has its update silently discarded.\n\nClear the two bits the reset is actually responsible for instead.\nRDS_IN_XMIT and RDS_RECV_REFILL need no store at all here: they\nbelong to the caller, rds_conn_shutdown(), which waits for both to be\nclear before calling the transport shutdown and this reset.\n\nThis also gives every bit in cp_flags a single well-defined writer\ndiscipline, which the following patches rely on when they turn\nRDS_IN_XMIT and RDS_RECV_REFILL into bit locks held across the\nteardown: a blanket store mid-teardown would destroy lock ownership\nthat an atomic clear preserves.\n\nOracle UEK carries the same conversion (\"net/rds: Preserve essential\nconnection state flags\"), motivated by its asynchronous shutdown\nstate machine, whose progress and destroy flags must survive the\nreset.  UEK's variant also clears RDS_IN_XMIT and RDS_RECV_REFILL\nbecause there the reset runs as the final step of a teardown that\nowns both bits, making those clears its unlock.  Upstream that\nrelease belongs in rds_conn_shutdown(): once a later patch in this\nseries turns the two bits into locks held across the teardown, ending\nownership needs release semantics and a wake-up that a plain clear\ninside the reset would not provide.\n\nBased on Oracle UEK commit \"net/rds: Preserve essential connection\nstate flags\" by Gerd Rausch.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98071"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/103c4b13c4f50322910078d1c02f29334a574122"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6b8d7563c28b8112e6e54abe413b028ef3f8c549"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b767b48614c38687d717082860de7aa46f3b142c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b7dc5da660eb5ffa7f7b4d33f2c74cb71c6edd6c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b8a8b6d25e7426a638c60eaba2129c0664131e84"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c9a7c1eb0ad41dcf004a9e870e452cafedcd9172"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cb62aa8f04655a4df487913949719c0a1266ed73"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ed3ee0ac4aafda50c2f4381eb973beefeb7879ac"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:36Z"
  }
}