CVE-2026-89670: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-86jr-9j73-5pc8
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-89670
GHSA Identifier GHSA-86jr-9j73-5pc8
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-89670

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-89670, 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: nfsd: hold rcu across localio cmpxchg retry nfsd_file objects are freed via call_rcu (filecache.c:296), and nfsd_file_slab is created without SLAB_TYPESAFE_BY_RCU (KMEM_CACHE(nfsd_file, 0) at filecache.c:789), so the slab page backing a freed nfsd_file becomes freely reclaimable once the RCU grace period elapses. The again: retry block in nfsd_open_local_fh() loads a pointer with cmpxchg and then calls nfsd_file_get(new) (which is refcount_inc_not_zero) without holding rcu_read_lock. The sole caller nfs_open_local_fh() drops rcu_read_lock before invoking this helper, so no outer reader-side critical section covers the load. CPU 0 (nfsd_open_local_fh) CPU 1 (nfsd_file_put_local) ----- ----- new = cmpxchg(pnf, NULL, ...) nf = xchg(pnf, NULL) nfsd_file_put(nf) last ref -> call_rcu() /* grace period elapses; slab page recycled */ nfsd_file_get(new) refcount_inc_not_zero(&new->nf_ref) /* operates on recycled memory */ A non-zero word at the nf_ref offset of the recycled object makes the refcount bump appear to succeed, and the caller then dereferences new->nf_net and new->nf_file out of freed memory. Fix by taking rcu_read_lock() immediately before the cmpxchg and releasing it on all three exits of the if (new) block: the goto-again retry, the lost-race cleanup path, and the install-succeeded path. nfsd_file_put() and nfsd_net_put() stay outside the RCU section so they remain free to block.

References

Frequently Asked Questions

What is CVE-2026-89670?
CVE-2026-89670 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-89670?
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-89670?
CVE-2026-89670 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-89670?
CVE-2026-89670 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89670?
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-86jr-9j73-5pc8",
  "modified" : "2026-09-13T09:32:27Z",
  "published" : "2026-09-11T21:31:35Z",
  "aliases" : [ "CVE-2026-89670" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: hold rcu across localio cmpxchg retry\n\nnfsd_file objects are freed via call_rcu (filecache.c:296), and\nnfsd_file_slab is created without SLAB_TYPESAFE_BY_RCU\n(KMEM_CACHE(nfsd_file, 0) at filecache.c:789), so the slab page\nbacking a freed nfsd_file becomes freely reclaimable once the RCU\ngrace period elapses.\n\nThe again: retry block in nfsd_open_local_fh() loads a pointer with\ncmpxchg and then calls nfsd_file_get(new) (which is\nrefcount_inc_not_zero) without holding rcu_read_lock. The sole caller\nnfs_open_local_fh() drops rcu_read_lock before invoking this helper,\nso no outer reader-side critical section covers the load.\n\n    CPU 0 (nfsd_open_local_fh)        CPU 1 (nfsd_file_put_local)\n    -----                             -----\n    new = cmpxchg(pnf, NULL, ...)\n                                      nf = xchg(pnf, NULL)\n                                      nfsd_file_put(nf)\n                                        last ref -> call_rcu()\n                                      /* grace period elapses;\n                                         slab page recycled */\n    nfsd_file_get(new)\n      refcount_inc_not_zero(&new->nf_ref)\n      /* operates on recycled memory */\n\nA non-zero word at the nf_ref offset of the recycled object makes the\nrefcount bump appear to succeed, and the caller then dereferences\nnew->nf_net and new->nf_file out of freed memory.\n\nFix by taking rcu_read_lock() immediately before the cmpxchg and\nreleasing it on all three exits of the if (new) block: the goto-again\nretry, the lost-race cleanup path, and the install-succeeded path.\nnfsd_file_put() and nfsd_net_put() stay outside the RCU section so\nthey remain free to block.",
  "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-89670"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/559570f91a7d4d199a72105e4980bef791f4cbf1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/58884694978a3d7d111edb433d7fd6a6c5af2f34"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/763c0bad872368304db718f79af7e93048885c67"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:53Z"
  }
}