CVE-2026-93107: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-86fh-qj8h-2fhq
Share
CVSS 8.2
Published
Advisory Summary

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

CVE-2026-93107 at a Glance

CVE Identifier CVE-2026-93107
GHSA Identifier GHSA-86fh-qj8h-2fhq
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability High (A:H)

How to Fix CVE-2026-93107

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-93107, 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: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state When do_complete() finds the QP in the error state it returns RESPST_CHK_RESOURCE. Before commit 49dc9c1f0c7e ("RDMA/rxe: Cleanup reset state handling in rxe_resp.c") this was the flush loop: check_resource() had an error-state branch that fetched each remaining recv WQE and completed it with IB_WC_WR_FLUSH_ERR, without touching the current packet. That commit removed the error-state branch from check_resource() (draining is now done at rxe_receiver() entry) but kept the do_complete() error-state return. As a result, when a QP moves to the error state while a packet is being completed - e.g. an rdma_cm disconnect racing with receive processing - the responder state machine loops back into the request processing chain with the already-completed packet still in hand: check_resource() fetches a fresh recv WQE, execute()/send_data_in() copies the same packet payload again, do_complete() posts another IB_WC_SUCCESS CQE (qp->resp.status is still 0), and control returns to the error-state check. The loop re-executes the same packet once per posted recv WQE (observed: ~1000 duplicate IB_WC_SUCCESS completions of one SEND, one per ~8us, matching the RQ occupancy) until the RQ is exhausted, after which qp->resp.wqe is NULL and send_data_in() dereferences it: BUG: kernel NULL pointer dereference, address: 0000000000000014 Workqueue: rxe_wq do_work RIP: copy_data+0x29/0x1f0 Call Trace: send_data_in+0x25/0x50 rxe_receiver+0xf36/0x1dd0 The duplicate completions are indistinguishable from real receives to the ULP. During an rds stress test, the message was accepted as new and delivered the same datagram to user space hundreds of times, corrupting the stream; any ULP that relies on RC exactly-once delivery is affected. A live packet reaching the error-state check in do_complete() has been executed and completed exactly once and must be consumed, not re-processed. Return RESPST_CLEANUP for it (dequeue and free); keep returning RESPST_CHK_RESOURCE for the pkt == NULL case.

References

NVD — CVE-2026-93107 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93107
git.kernel.org/stable/c/0d37e2503e... WEB
https://git.kernel.org/stable/c/0d37e2503efd1069a74be740eadf63ea17c96810
git.kernel.org/stable/c/15ae32c4a3... WEB
https://git.kernel.org/stable/c/15ae32c4a3551c4c9da457370bdfdd65d171e512
git.kernel.org/stable/c/399713f1f0... WEB
https://git.kernel.org/stable/c/399713f1f0eac641351c8ceaec0ab8244ddcf78c
git.kernel.org/stable/c/62a4b48767... WEB
https://git.kernel.org/stable/c/62a4b48767e06fdd64548450fae2b1ffc6ff5d69
git.kernel.org/stable/c/c319b986a8... WEB
https://git.kernel.org/stable/c/c319b986a88cedf600c4497cd7814a891b2f9e7c

Frequently Asked Questions

What is CVE-2026-93107?
CVE-2026-93107 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-93107?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-93107?
CVE-2026-93107 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H.
What CWE is associated with CVE-2026-93107?
CVE-2026-93107 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93107?
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-86fh-qj8h-2fhq",
  "modified" : "2026-09-18T18:31:34Z",
  "published" : "2026-09-17T18:32:10Z",
  "aliases" : [ "CVE-2026-93107" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state\n\nWhen do_complete() finds the QP in the error state it returns\nRESPST_CHK_RESOURCE.  Before commit 49dc9c1f0c7e (\"RDMA/rxe: Cleanup\nreset state handling in rxe_resp.c\") this was the flush loop:\ncheck_resource() had an error-state branch that fetched each remaining\nrecv WQE and completed it with IB_WC_WR_FLUSH_ERR, without touching\nthe current packet.  That commit removed the error-state branch from\ncheck_resource() (draining is now done at rxe_receiver() entry) but\nkept the do_complete() error-state return.\n\nAs a result, when a QP moves to the error state while a packet is\nbeing completed - e.g. an rdma_cm disconnect racing with receive\nprocessing - the responder state machine loops back into the request\nprocessing chain with the already-completed packet still in hand:\ncheck_resource() fetches a fresh recv WQE, execute()/send_data_in()\ncopies the same packet payload again, do_complete() posts another\nIB_WC_SUCCESS CQE (qp->resp.status is still 0), and control returns\nto the error-state check.  The loop re-executes the same packet once\nper posted recv WQE (observed: ~1000 duplicate IB_WC_SUCCESS\ncompletions of one SEND, one per ~8us, matching the RQ occupancy)\nuntil the RQ is exhausted, after which qp->resp.wqe is NULL and\nsend_data_in() dereferences it:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000014\n  Workqueue: rxe_wq do_work\n  RIP: copy_data+0x29/0x1f0\n  Call Trace:\n   send_data_in+0x25/0x50\n   rxe_receiver+0xf36/0x1dd0\n\nThe duplicate completions are indistinguishable from real receives to\nthe ULP.  During an rds stress test, the message was accepted as new and\ndelivered the same datagram to user space hundreds of times, corrupting\nthe stream; any ULP that relies on RC exactly-once delivery is affected.\n\nA live packet reaching the error-state check in do_complete() has\nbeen executed and completed exactly once and must be consumed, not\nre-processed.  Return RESPST_CLEANUP for it (dequeue and free); keep\nreturning RESPST_CHK_RESOURCE for the pkt == NULL case.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93107"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0d37e2503efd1069a74be740eadf63ea17c96810"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/15ae32c4a3551c4c9da457370bdfdd65d171e512"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/399713f1f0eac641351c8ceaec0ab8244ddcf78c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/62a4b48767e06fdd64548450fae2b1ffc6ff5d69"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c319b986a88cedf600c4497cd7814a891b2f9e7c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:18:05Z"
  }
}