CVE-2026-89718: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-8g3j-f4r3-9992
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89718
GHSA Identifier GHSA-8g3j-f4r3-9992
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-89718

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-89718, 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: zram: fix out-of-bounds access in writeback_store() Patch series "zram: fix stale scan bounds after reinitialization". Both writeback_store() and read_block_state() derive their table scan bounds from zram->disksize before acquiring dev_lock. If the device is reset and reinitialized with a smaller disksize between that read and lock acquisition, the bound can describe the old table while the scan operates on the new one. This can lead to out-of-bounds slot accesses. Move both bound calculations under dev_lock so each bound remains consistent with the table throughout its scan. Keep the fixes separate because the affected interfaces originate from different commits and can be backported independently. This patch (of 2): writeback_store() calculates the table scan bounds before taking dev_lock. A reset followed by reconfiguration with a smaller disksize can therefore replace zram->table while writeback_store() is waiting for the lock. Once it acquires the lock, it sees an initialized device but scans the new table using the old upper bound, resulting in an out-of-bounds access. Calculate the number of pages while holding dev_lock so the scan bound matches the table protected by the lock.

References

NVD — CVE-2026-89718 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89718
git.kernel.org/stable/c/07a82a66f8... WEB
https://git.kernel.org/stable/c/07a82a66f8c1894d92e51d97542c32ebf2c51b09
git.kernel.org/stable/c/4d82d60178... WEB
https://git.kernel.org/stable/c/4d82d60178b02797dbe529e01ac211b26670c49f
git.kernel.org/stable/c/894913e2d3... WEB
https://git.kernel.org/stable/c/894913e2d35c46ff19a77530907771ae57862b96
git.kernel.org/stable/c/ef073edd7c... WEB
https://git.kernel.org/stable/c/ef073edd7cfd31aeb90eeab23273102c601f4d8e

Frequently Asked Questions

What is CVE-2026-89718?
CVE-2026-89718 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-89718?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89718?
CVE-2026-89718 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89718?
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-8g3j-f4r3-9992",
  "modified" : "2026-10-15T12:30:46Z",
  "published" : "2026-09-11T21:31:37Z",
  "aliases" : [ "CVE-2026-89718" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nzram: fix out-of-bounds access in writeback_store()\n\nPatch series \"zram: fix stale scan bounds after reinitialization\".\n\nBoth writeback_store() and read_block_state() derive their table scan\nbounds from zram->disksize before acquiring dev_lock.  If the device is\nreset and reinitialized with a smaller disksize between that read and lock\nacquisition, the bound can describe the old table while the scan operates\non the new one.  This can lead to out-of-bounds slot accesses.\n\nMove both bound calculations under dev_lock so each bound remains\nconsistent with the table throughout its scan.  Keep the fixes separate\nbecause the affected interfaces originate from different commits and can\nbe backported independently.\n\n\nThis patch (of 2):\n\nwriteback_store() calculates the table scan bounds before taking dev_lock.\nA reset followed by reconfiguration with a smaller disksize can therefore\nreplace zram->table while writeback_store() is waiting for the lock.  Once\nit acquires the lock, it sees an initialized device but scans the new\ntable using the old upper bound, resulting in an out-of-bounds access.\n\nCalculate the number of pages while holding dev_lock so the scan bound\nmatches the table protected by the lock.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89718"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/07a82a66f8c1894d92e51d97542c32ebf2c51b09"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4d82d60178b02797dbe529e01ac211b26670c49f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/894913e2d35c46ff19a77530907771ae57862b96"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ef073edd7cfd31aeb90eeab23273102c601f4d8e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:59Z"
  }
}