CVE-2026-98361: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-g3wm-757g-9p35
CVSS 7.8
Published
Advisory Summary

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

CVE-2026-98361 at a Glance

CVE Identifier CVE-2026-98361
GHSA Identifier GHSA-g3wm-757g-9p35
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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

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

How to Fix CVE-2026-98361

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-98361, 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: Restore HMM_PFN_WRITE check in ODP write paths Commit 0b261d7c1cd3 ("RDMA/rxe: Break endless pagefault loop for RO pages") dropped the access permission test from rxe_check_pagefault() and left only HMM_PFN_VALID. A page faulted in read-only, for example a page-cache folio behind a PROT_READ file mapping, then satisfies the check and ODP write operations (RDMA WRITE, RDMA READ response, SEND payload, atomics) modify it through kmap without ever breaking CoW. An unprivileged user can register an ODP MR over such a mapping and have incoming RDMA traffic overwrite the page cache of a file it only holds O_RDONLY, including /etc/passwd or setuid binaries. This is the same primitive class as Dirty COW and CVE-2022-2590. mlx5 has the missing invariant: its ODP path sets the device write bit only for pfns that carry HMM_PFN_WRITE. Restore it in rxe by requiring HMM_PFN_WRITE in rxe_check_pagefault() for every operation except RXE_PAGEFAULT_RDONLY. A write to a non-writable VMA now fails the one fault attempt with -EPERM from hmm_vma_fault() instead of re-faulting forever. For a writable VMA the fault breaks CoW and the write lands in the private page. Keep pmem flushes on the read-only check. arch_wb_cache_pmem() never modifies memory, and the FLUSH access bits do not make the umem writable, so classifying flushes as writes would make every flush against a flush-only MR fail.

References

Frequently Asked Questions

What is CVE-2026-98361?
CVE-2026-98361 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-98361?
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-98361?
CVE-2026-98361 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-98361?
CVE-2026-98361 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98361?
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-g3wm-757g-9p35",
  "modified" : "2026-10-07T09:32:17Z",
  "published" : "2026-10-06T09:31:36Z",
  "aliases" : [ "CVE-2026-98361" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Restore HMM_PFN_WRITE check in ODP write paths\n\nCommit 0b261d7c1cd3 (\"RDMA/rxe: Break endless pagefault loop for RO\npages\") dropped the access permission test from rxe_check_pagefault()\nand left only HMM_PFN_VALID. A page faulted in read-only, for example\na page-cache folio behind a PROT_READ file mapping, then satisfies the\ncheck and ODP write operations (RDMA WRITE, RDMA READ response, SEND\npayload, atomics) modify it through kmap without ever breaking CoW.\n\nAn unprivileged user can register an ODP MR over such a mapping and\nhave incoming RDMA traffic overwrite the page cache of a file it only\nholds O_RDONLY, including /etc/passwd or setuid binaries. This is the\nsame primitive class as Dirty COW and CVE-2022-2590.\n\nmlx5 has the missing invariant: its ODP path sets the device write bit\nonly for pfns that carry HMM_PFN_WRITE. Restore it in rxe by requiring\nHMM_PFN_WRITE in rxe_check_pagefault() for every operation except\nRXE_PAGEFAULT_RDONLY. A write to a non-writable VMA now fails the one\nfault attempt with -EPERM from hmm_vma_fault() instead of re-faulting\nforever. For a writable VMA the fault breaks CoW and the write lands\nin the private page.\n\nKeep pmem flushes on the read-only check. arch_wb_cache_pmem() never\nmodifies memory, and the FLUSH access bits do not make the umem\nwritable, so classifying flushes as writes would make every flush\nagainst a flush-only MR fail.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98361"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2d6c6f94d3e1cde049fe5db71dbd5549f10b2de1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/769001ce838d907ecaa95f1d0a4e8fc86f761f9f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c6f56982ec5c7da83c4bdfcce3b6db18bcfe6425"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-06T09:18:29Z"
  }
}