CVE-2026-89646: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-q4q8-9c96-gj73
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-89646
GHSA Identifier GHSA-q4q8-9c96-gj73
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-89646

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-89646, 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: ceph: fix leaked inode reference on writeback abort at umount ceph_dirty_folio() takes a wrbuffer claim on each newly dirtied folio: it bumps i_wrbuffer_ref (taking an ihold() on the 0->1 transition) and attaches the snap_context to folio->private. That claim is released only by ceph_put_wrbuffer_cap_refs(), which for a submitted write runs from writepages_finish(). In ceph_submit_write(), if ceph_inc_osd_stopping_blocker() fails -- which happens during umount -- the request is aborted before submission: the already-collected folios are only redirtied and unlocked, so writepages_finish() never runs and the claim is leaked. redirty_page_for_writepage() -> folio_redirty_for_writepage() -> filemap_dirty_folio() sets PG_dirty directly and does not go through ->dirty_folio, so ceph_dirty_folio() is not re-entered to rebalance it. Because every subsequent writeback also fails the osd_stopping_blocker, i_wrbuffer_ref never returns to 0, the ihold() is never dropped, and the inode cannot be evicted: VFS: Busy inodes after unmount of ceph kernel BUG at fs/super.c:650! Release the orphaned claim in the abort path before redirtying, via ceph_undo_wrbuffer_claim(): detach the snap_context, drop the wrbuffer reference (letting i_wrbuffer_ref reach 0 and iput() the inode), and drop the snap_context reference -- i.e. do what writepages_finish() would have done for these never-submitted folios. Only the locked_pages entries are undone; folios still in the fbatch were never dirty-cleared by this call (folio_clear_dirty_for_io() is the ownership-transfer point, and a successful move NULLs the fbatch slot), so they hold no claim this call owns.

References

NVD — CVE-2026-89646 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89646
git.kernel.org/stable/c/ac7a5a5385... WEB
https://git.kernel.org/stable/c/ac7a5a5385762df458d10cccc086a4e079be7409
git.kernel.org/stable/c/c25aee9c63... WEB
https://git.kernel.org/stable/c/c25aee9c630fb86f98d79eccb75765067079b972
git.kernel.org/stable/c/ec32015a95... WEB
https://git.kernel.org/stable/c/ec32015a955c5d326c5e26610edfdcccd52f2314

Frequently Asked Questions

What is CVE-2026-89646?
CVE-2026-89646 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-89646?
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-89646?
CVE-2026-89646 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-89646?
CVE-2026-89646 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89646?
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-q4q8-9c96-gj73",
  "modified" : "2026-09-13T09:32:26Z",
  "published" : "2026-09-11T21:31:35Z",
  "aliases" : [ "CVE-2026-89646" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix leaked inode reference on writeback abort at umount\n\nceph_dirty_folio() takes a wrbuffer claim on each newly dirtied folio: it\nbumps i_wrbuffer_ref (taking an ihold() on the 0->1 transition) and\nattaches the snap_context to folio->private.  That claim is released only\nby ceph_put_wrbuffer_cap_refs(), which for a submitted write runs from\nwritepages_finish().\n\nIn ceph_submit_write(), if ceph_inc_osd_stopping_blocker() fails -- which\nhappens during umount -- the request is aborted before submission: the\nalready-collected folios are only redirtied and unlocked, so\nwritepages_finish() never runs and the claim is leaked.\nredirty_page_for_writepage() -> folio_redirty_for_writepage() ->\nfilemap_dirty_folio() sets PG_dirty directly and does not go through\n->dirty_folio, so ceph_dirty_folio() is not re-entered to rebalance it.\nBecause every subsequent writeback also fails the osd_stopping_blocker,\ni_wrbuffer_ref never returns to 0, the ihold() is never dropped, and the\ninode cannot be evicted:\n\n  VFS: Busy inodes after unmount of ceph\n  kernel BUG at fs/super.c:650!\n\nRelease the orphaned claim in the abort path before redirtying, via\nceph_undo_wrbuffer_claim(): detach the snap_context, drop the wrbuffer\nreference (letting i_wrbuffer_ref reach 0 and iput() the inode), and drop\nthe snap_context reference -- i.e. do what writepages_finish() would have\ndone for these never-submitted folios.\n\nOnly the locked_pages entries are undone; folios still in the fbatch were\nnever dirty-cleared by this call (folio_clear_dirty_for_io() is the\nownership-transfer point, and a successful move NULLs the fbatch slot), so\nthey hold no claim this call owns.",
  "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-89646"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ac7a5a5385762df458d10cccc086a4e079be7409"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c25aee9c630fb86f98d79eccb75765067079b972"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ec32015a955c5d326c5e26610edfdcccd52f2314"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:50Z"
  }
}