CVE-2026-98023: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-vcqm-xvp9-x4jq
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-98023
GHSA Identifier GHSA-vcqm-xvp9-x4jq
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-98023

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-98023, 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: vxlan: reject dynamic fdb entries that reference a nexthop id The commit cited in the Fixes tag allowed VXLAN FDB entries to point to FDB nexthops so that overlay traffic could be load balanced across multiple VTEPs. Such entries can only be configured from user space, cannot be learned and cannot roam. They only make sense with a user space control plane such as E-VPN where data plane learning is disabled. Despite that, the VXLAN driver does not currently prevent such entries from being configured with the "dynamic" flag. The per-nexthop FDB list is only protected by the per-device hash lock, which is not sufficient when two VXLAN devices point to the same FDB nexthop and therefore share the list. Aging runs in softirq context without RTNL, so an entry deleted by one device can race with an addition or deletion from the other, leading to list corruption: list_del corruption. next->prev should be ffff8881069d9548, but was dead000000000122. (next=ffff8881069d9448) WARNING: CPU: 0 PID: 90 at lib/list_debug.c:65 __list_del_entry_valid_or_report+0x1aa/0x210 ... vxlan_fdb_destroy+0x5b8/0xad0 vxlan_cleanup+0x328/0x450 call_timer_fn+0x2a/0x1c0 run_timer_softirq+0x18c/0x210 BUG: KASAN: slab-use-after-free in vxlan_fdb_destroy Fix this by rejecting the bogus configuration of dynamic FDB entries that point to FDB nexthops, both when created and when an existing entry is updated. As such, the per-nexthop FDB list is only ever mutated under the RTNL lock. Add test cases to make sure that this does not regress in the future.

References

NVD — CVE-2026-98023 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98023
git.kernel.org/stable/c/00c7f4b814... WEB
https://git.kernel.org/stable/c/00c7f4b8144e535ffb931ad45942a1bd1315b882
git.kernel.org/stable/c/28f86eec85... WEB
https://git.kernel.org/stable/c/28f86eec851b7406a4bc6143f82aeba2882d9842
git.kernel.org/stable/c/3fa64d86fc... WEB
https://git.kernel.org/stable/c/3fa64d86fc64eda104e3e97721a12a42a2fd2073
git.kernel.org/stable/c/53359916ce... WEB
https://git.kernel.org/stable/c/53359916ceb649b7e6947c8c2f669368a41c1354
git.kernel.org/stable/c/55a3388280... WEB
https://git.kernel.org/stable/c/55a33882808f1402052d53a08ead59aff8af18a1
git.kernel.org/stable/c/98fc57d167... WEB
https://git.kernel.org/stable/c/98fc57d167446b95b4e719815fe79edef93f8e7a
git.kernel.org/stable/c/b2a8e165dd... WEB
https://git.kernel.org/stable/c/b2a8e165ddb6cd72176890b2954c52b0f6dbce1a
git.kernel.org/stable/c/c8f29af91e... WEB
https://git.kernel.org/stable/c/c8f29af91e0830fdabc9aa1eb1a0f898ce1bc603

Frequently Asked Questions

What is CVE-2026-98023?
CVE-2026-98023 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-98023?
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-98023?
CVE-2026-98023 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-98023?
CVE-2026-98023 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98023?
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-vcqm-xvp9-x4jq",
  "modified" : "2026-10-03T12:31:24Z",
  "published" : "2026-09-25T12:31:33Z",
  "aliases" : [ "CVE-2026-98023" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: reject dynamic fdb entries that reference a nexthop id\n\nThe commit cited in the Fixes tag allowed VXLAN FDB entries to point to\nFDB nexthops so that overlay traffic could be load balanced across\nmultiple VTEPs. Such entries can only be configured from user space,\ncannot be learned and cannot roam. They only make sense with a user space\ncontrol plane such as E-VPN where data plane learning is disabled.\n\nDespite that, the VXLAN driver does not currently prevent such entries\nfrom being configured with the \"dynamic\" flag. The per-nexthop FDB list\nis only protected by the per-device hash lock, which is not sufficient\nwhen two VXLAN devices point to the same FDB nexthop and therefore share\nthe list. Aging runs in softirq context without RTNL, so an entry deleted\nby one device can race with an addition or deletion from the other,\nleading to list corruption:\n\n  list_del corruption. next->prev should be ffff8881069d9548, but was\n  dead000000000122. (next=ffff8881069d9448)\n  WARNING: CPU: 0 PID: 90 at lib/list_debug.c:65\n  __list_del_entry_valid_or_report+0x1aa/0x210\n  ...\n   vxlan_fdb_destroy+0x5b8/0xad0\n   vxlan_cleanup+0x328/0x450\n   call_timer_fn+0x2a/0x1c0\n   run_timer_softirq+0x18c/0x210\n  BUG: KASAN: slab-use-after-free in vxlan_fdb_destroy\n\nFix this by rejecting the bogus configuration of dynamic FDB entries that\npoint to FDB nexthops, both when created and when an existing entry is\nupdated. As such, the per-nexthop FDB list is only ever mutated under the\nRTNL lock. Add test cases to make sure that this does not regress in the\nfuture.",
  "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-98023"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/00c7f4b8144e535ffb931ad45942a1bd1315b882"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/28f86eec851b7406a4bc6143f82aeba2882d9842"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3fa64d86fc64eda104e3e97721a12a42a2fd2073"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/53359916ceb649b7e6947c8c2f669368a41c1354"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/55a33882808f1402052d53a08ead59aff8af18a1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/98fc57d167446b95b4e719815fe79edef93f8e7a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b2a8e165ddb6cd72176890b2954c52b0f6dbce1a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c8f29af91e0830fdabc9aa1eb1a0f898ce1bc603"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:30Z"
  }
}