CVE-2026-89947: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-8jgg-jgf5-2v4q
CVSS 8.0
Published
Advisory Summary

CVE-2026-89947 is a HIGH (CVSS 8.0) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-89947 at a Glance

CVE Identifier CVE-2026-89947
GHSA Identifier GHSA-8jgg-jgf5-2v4q
Severity HIGH
CVSS v3.1 Base Score 8.0
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability High (A:H)

How to Fix CVE-2026-89947

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-89947, 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: clk: meson: align gxbb_32k_clk_sel number of parents with actual count The following out-of-bounds read has been observed by Christian on a GXBB WeTek Hub: ================================================================== BUG: KASAN: global-out-of-bounds in __clk_register+0x1b70/0x2418 Read of size 8 at addr ffffd66320cf88e0 by task swapper/0/1 CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc5 #1 PREEMPT Hardware name: WeTek Hub (DT) Call trace: show_stack+0x14/0x20 (C) dump_stack_lvl+0x74/0x94 print_report+0x164/0x4b0 kasan_report+0x98/0xd8 __asan_report_load8_noabort+0x1c/0x24 __clk_register+0x1b70/0x2418 devm_clk_hw_register+0x74/0x15c meson_clkc_init+0xd4/0x20c meson_clkc_syscon_probe+0x5c/0x94 platform_probe+0xbc/0x17c really_probe+0x184/0x844 __driver_probe_device+0x154/0x35c driver_probe_device+0x60/0x188 __driver_attach+0x168/0x4a0 bus_for_each_dev+0xec/0x180 driver_attach+0x38/0x58 bus_add_driver+0x238/0x4c0 driver_register+0x150/0x388 __platform_driver_register+0x54/0x7c gxbb_clkc_driver_init+0x18/0x20 do_one_initcall+0xb8/0x340 kernel_init_freeable+0x49c/0x52c kernel_init+0x24/0x148 ret_from_fork+0x10/0x20 The buggy address belongs to the variable: gxbb_32k_clk_parents+0x60/0x400 The buggy address belongs to a vmalloc virtual mapping The buggy address belongs to the physical page: Memory state around the buggy address: ffffd66320cf8780: 00 00 00 00 f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9 ffffd66320cf8800: 00 04 f9 f9 f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 >ffffd66320cf8880: 00 00 00 00 00 00 00 00 00 00 00 00 f9 f9 f9 f9 ^ ffffd66320cf8900: 00 01 f9 f9 f9 f9 f9 f9 00 06 f9 f9 f9 f9 f9 f9 ffffd66320cf8980: 00 00 02 f9 f9 f9 f9 f9 00 00 02 f9 f9 f9 f9 f9 ================================================================== Commit 7915d7d5407c ("clk: amlogic: gxbb: drop non existing 32k clock parent") dropped a non-existing clock parent from the gxbb_32k_clk_sel mux but didn't adjust the hard-coded num_parents field. Fix the actual number of parents of that mux by using ARRAY_SIZE instead (avoiding similar problems in future).

References

Frequently Asked Questions

What is CVE-2026-89947?
CVE-2026-89947 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-89947?
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-89947?
CVE-2026-89947 has a CVSS v3.1 base score of 8.0 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H.
What CWE is associated with CVE-2026-89947?
CVE-2026-89947 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89947?
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-8jgg-jgf5-2v4q",
  "modified" : "2026-09-16T15:31:03Z",
  "published" : "2026-09-16T12:30:42Z",
  "aliases" : [ "CVE-2026-89947" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: meson: align gxbb_32k_clk_sel number of parents with actual count\n\nThe following out-of-bounds read has been observed by Christian on a\nGXBB WeTek Hub:\n==================================================================\nBUG: KASAN: global-out-of-bounds in __clk_register+0x1b70/0x2418\nRead of size 8 at addr ffffd66320cf88e0 by task swapper/0/1\n\nCPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc5 #1 PREEMPT\nHardware name: WeTek Hub (DT)\nCall trace:\n show_stack+0x14/0x20 (C)\n dump_stack_lvl+0x74/0x94\n print_report+0x164/0x4b0\n kasan_report+0x98/0xd8\n __asan_report_load8_noabort+0x1c/0x24\n __clk_register+0x1b70/0x2418\n devm_clk_hw_register+0x74/0x15c\n meson_clkc_init+0xd4/0x20c\n meson_clkc_syscon_probe+0x5c/0x94\n platform_probe+0xbc/0x17c\n really_probe+0x184/0x844\n __driver_probe_device+0x154/0x35c\n driver_probe_device+0x60/0x188\n __driver_attach+0x168/0x4a0\n bus_for_each_dev+0xec/0x180\n driver_attach+0x38/0x58\n bus_add_driver+0x238/0x4c0\n driver_register+0x150/0x388\n __platform_driver_register+0x54/0x7c\n gxbb_clkc_driver_init+0x18/0x20\n do_one_initcall+0xb8/0x340\n kernel_init_freeable+0x49c/0x52c\n kernel_init+0x24/0x148\n ret_from_fork+0x10/0x20\n\nThe buggy address belongs to the variable:\n gxbb_32k_clk_parents+0x60/0x400\n\nThe buggy address belongs to a vmalloc virtual mapping\nThe buggy address belongs to the physical page:\n\nMemory state around the buggy address:\n ffffd66320cf8780: 00 00 00 00 f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9\n ffffd66320cf8800: 00 04 f9 f9 f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9\n>ffffd66320cf8880: 00 00 00 00 00 00 00 00 00 00 00 00 f9 f9 f9 f9\n                                                       ^\n ffffd66320cf8900: 00 01 f9 f9 f9 f9 f9 f9 00 06 f9 f9 f9 f9 f9 f9\n ffffd66320cf8980: 00 00 02 f9 f9 f9 f9 f9 00 00 02 f9 f9 f9 f9 f9\n==================================================================\n\nCommit 7915d7d5407c (\"clk: amlogic: gxbb: drop non existing 32k clock\nparent\") dropped a non-existing clock parent from the gxbb_32k_clk_sel\nmux but didn't adjust the hard-coded num_parents field. Fix the actual\nnumber of parents of that mux by using ARRAY_SIZE instead (avoiding\nsimilar problems in future).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89947"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1e509a6707d2fd9da79bdfa24742661b34562bfd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/404079d124d75a5da16322acc53d3ffc50b4ec68"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4582949b7badcb91bb537ca522d69b8a35131e72"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/628b6fee9fca292f12d07f0f1bcf1edefa949d81"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8b2f7a411e7ceaef268355c2150c22ee3f509c3b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bf85bd6e550c17ffa585606fcc18eb5b7c95bbce"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c86214e6178c38a0eff39110a4e92b824f5dd403"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f6ff0e6995dbff5cb145d7795c8f0af9c168094a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:04Z"
  }
}