CVE-2026-89803: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-6w43-3678-pp8f
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-89803
GHSA Identifier GHSA-6w43-3678-pp8f
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-89803

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-89803, 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: drm/nouveau: unsubscribe the channel-kill event before the fence context nouveau_channel_del() tears the fence context down first and only drops the channel-kill subscription later, in the middle of the nvif object teardown: if (chan->fence) nouveau_fence(chan->cli->drm)->context_del(chan); ... nvif_object_dtor(&chan->vram); nvif_event_dtor(&chan->kill); The subscribed handler is nouveau_channel_killed(), which calls nouveau_channel_kill() and from there nouveau_fence_context_kill() on chan->fence. A kill event delivered in that window takes fctx->lock and walks fctx->pending on a fence context that context_del() has already freed. Nothing reaches this below Fermi today, because the subscription is gated on FERMI_CHANNEL_GPFIFO and nothing kills a channel there. On Fermi and newer the window is real but narrow, since a kill has to land exactly while the channel is being destroyed. That is reason enough on its own, which is why this carries a Fixes: tag. The last patch in this series subscribes Tesla channels as well; nothing kills those today, so it does not widen the exposure now, but it is the groundwork for a recovery path that would, and the ordering is better fixed before that lands than alongside it. Drop the subscription before anything it depends on is torn down.

References

NVD — CVE-2026-89803 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89803
git.kernel.org/stable/c/1fef7553dc... WEB
https://git.kernel.org/stable/c/1fef7553dc628295c1208a4f2ac2094c62886e5d
git.kernel.org/stable/c/511585987d... WEB
https://git.kernel.org/stable/c/511585987d27d8cb668acebd399fc4deda23404c
git.kernel.org/stable/c/f3830fdd69... WEB
https://git.kernel.org/stable/c/f3830fdd6930e233d727f29eee1617f7e6a0e9e5
git.kernel.org/stable/c/f5a79a9ebf... WEB
https://git.kernel.org/stable/c/f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e

Frequently Asked Questions

What is CVE-2026-89803?
CVE-2026-89803 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-89803?
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-89803?
CVE-2026-89803 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-89803?
CVE-2026-89803 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89803?
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-6w43-3678-pp8f",
  "modified" : "2026-09-16T15:30:57Z",
  "published" : "2026-09-16T12:30:36Z",
  "aliases" : [ "CVE-2026-89803" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau: unsubscribe the channel-kill event before the fence context\n\nnouveau_channel_del() tears the fence context down first and only drops\nthe channel-kill subscription later, in the middle of the nvif object\nteardown:\n\n\tif (chan->fence)\n\t\tnouveau_fence(chan->cli->drm)->context_del(chan);\n\t...\n\tnvif_object_dtor(&chan->vram);\n\tnvif_event_dtor(&chan->kill);\n\nThe subscribed handler is nouveau_channel_killed(), which calls\nnouveau_channel_kill() and from there nouveau_fence_context_kill() on\nchan->fence. A kill event delivered in that window takes fctx->lock and\nwalks fctx->pending on a fence context that context_del() has already\nfreed.\n\nNothing reaches this below Fermi today, because the subscription is\ngated on FERMI_CHANNEL_GPFIFO and nothing kills a channel there. On\nFermi and newer the window is real but narrow, since a kill has to land\nexactly while the channel is being destroyed. That is reason enough on\nits own, which is why this carries a Fixes: tag. The last patch in this\nseries subscribes Tesla channels as well; nothing kills those today, so\nit does not widen the exposure now, but it is the groundwork for a\nrecovery path that would, and the ordering is better fixed before that\nlands than alongside it.\n\nDrop the subscription before anything it depends on is torn down.",
  "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-89803"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1fef7553dc628295c1208a4f2ac2094c62886e5d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/511585987d27d8cb668acebd399fc4deda23404c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f3830fdd6930e233d727f29eee1617f7e6a0e9e5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:16:45Z"
  }
}