CVE-2026-74299: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-j69g-mrr3-p2qh
Published
Advisory Summary

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

CVE Identifier CVE-2026-74299
GHSA Identifier GHSA-j69g-mrr3-p2qh
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-74299

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-74299, 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/core: Fix FRMR aging push to queue error flow Aging pools with pinned handles requires moving handles from the active queue to a non-empty inactive queue that might fail on new page allocation, we are currently not handling the fault and leaking any mkey that fails the push. Fix by Introducing push_queue_to_queue_locked() that fills the destination's partial tail page from the source and then splices the remaining source pages onto the destination, performing no allocation. Replace the per-handle move loop in age_pinned_pool() and the open-coded splice in pool_aging_work() with calls to the helper. As the helper cannot fail under memory pressure, removing a class of GFP_ATOMIC allocations under the pool lock and simplifying the error flow.

References

Frequently Asked Questions

What is CVE-2026-74299?
CVE-2026-74299 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-74299?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-74299?
CVE-2026-74299 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-74299?
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-j69g-mrr3-p2qh",
  "modified" : "2026-08-15T06:32:28Z",
  "published" : "2026-08-15T06:32:28Z",
  "aliases" : [ "CVE-2026-74299" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Fix FRMR aging push to queue error flow\n\nAging pools with pinned handles requires moving handles from the\nactive queue to a non-empty inactive queue that might fail on new page\nallocation, we are currently not handling the fault and leaking any mkey\nthat fails the push.\n\nFix by Introducing push_queue_to_queue_locked() that fills the\ndestination's partial tail page from the source and then splices the\nremaining source pages onto the destination, performing no allocation.\n\nReplace the per-handle move loop in age_pinned_pool() and the\nopen-coded splice in pool_aging_work() with calls to the helper.\nAs the helper cannot fail under memory pressure, removing a class of\nGFP_ATOMIC allocations under the pool lock and simplifying the error\nflow.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-74299"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c6936506ed556ce3ccad36ab999baf2764dd7d25"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/edf133d28fc43f7f8b0da43a8d5b93fdf8073d35"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:29Z"
  }
}