CVE-2026-98588: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-v3gv-6qr6-4mh5
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98588
GHSA Identifier GHSA-v3gv-6qr6-4mh5
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-98588

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-98588, 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: bpf, sockmap: Reject max_entries > INT_MAX in sock_map_alloc sock_map_alloc() only rejects max_entries == 0 and otherwise allows any u32 value. sock_map_free() then walks the sks[] array with a signed int iterator: int i; for (i = 0; i < stab->map.max_entries; i++) struct sock **psk = &stab->sks[i]; When a SOCKMAP is created with max_entries = 0xffffffff (UINT_MAX), the allocation of 32 GiB can succeed on large-memory hosts. During free the counter reaches 0x80000000, wraps to INT_MIN, is sign-extended by movslq and turned into a ~16 GiB negative offset from stab->sks, pointing far below the allocation. The faulting access is an xchg() write in sock_map_free(). Without KASAN, the same out-of-bounds write can fault on an unmapped vmalloc page or corrupt an unrelated allocation if that vmalloc address is populated. On a KASAN kernel with CONFIG_KASAN_VMALLOC=y, the shadow check for that address hits an unmapped shadow page and oopses first: BUG: unable to handle page fault for address: fffff521b59c5a00 RIP: 0010:kasan_check_range+0x107/0x190 Call Trace: sock_map_free+0x93/0x190 map_create+0x68d/0xb30 __sys_bpf+0x21e/0x2e70 Vmcore confirmed stab->map.max_entries == 0xffffffff, stab->sks == 0xffffc911ace2d000, and the faulting address sks + (s64)INT_MIN * 8 exactly at 0xffffc90dace2d000. The same buggy path is reached on the normal close()/bpf_map_free_deferred() path whenever such a map is destroyed. sock_map_alloc() used to bound its allocation size through bpf_map_charge_init(), but the bound was dropped when rlimit-based memory accounting was removed. Reject max_entries > INT_MAX at creation time so the signed iterator in sock_map_free() never sees a value that would overflow. Triggered by syzkaller and reproduced on both a 6.6-based KASAN kernel and the upstream v7.3-rc2 kernel.

References

NVD — CVE-2026-98588 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98588
git.kernel.org/stable/c/814a81c842... WEB
https://git.kernel.org/stable/c/814a81c842bd88f6bd8a4ce550d560df071a5d03
git.kernel.org/stable/c/909f761868... WEB
https://git.kernel.org/stable/c/909f761868fda329dc69130ef9eb5b5795bcdf00
git.kernel.org/stable/c/ba7d627dbc... WEB
https://git.kernel.org/stable/c/ba7d627dbc67d62df2fa66d7b41e743c3ace0ec8
git.kernel.org/stable/c/c56191af3a... WEB
https://git.kernel.org/stable/c/c56191af3a578b9cc265fa3bd5fc0752c59c1781
git.kernel.org/stable/c/cc70972ddb... WEB
https://git.kernel.org/stable/c/cc70972ddbf0e3398f2f32624d31db78594d50d8
git.kernel.org/stable/c/cea597519b... WEB
https://git.kernel.org/stable/c/cea597519b9ca6d691c98d92460ead8ece2a07af
git.kernel.org/stable/c/f4a73f49e2... WEB
https://git.kernel.org/stable/c/f4a73f49e256bd835368504462be3b57b03febff

Frequently Asked Questions

What is CVE-2026-98588?
CVE-2026-98588 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-98588?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98588?
CVE-2026-98588 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98588?
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-v3gv-6qr6-4mh5",
  "modified" : "2026-10-18T18:31:55Z",
  "published" : "2026-10-18T18:31:55Z",
  "aliases" : [ "CVE-2026-98588" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf, sockmap: Reject max_entries > INT_MAX in sock_map_alloc\n\nsock_map_alloc() only rejects max_entries == 0 and otherwise allows any\nu32 value.  sock_map_free() then walks the sks[] array with a signed int\niterator:\n\n\tint i;\n\tfor (i = 0; i < stab->map.max_entries; i++)\n\t\tstruct sock **psk = &stab->sks[i];\n\nWhen a SOCKMAP is created with max_entries = 0xffffffff (UINT_MAX), the\nallocation of 32 GiB can succeed on large-memory hosts.  During free the\ncounter reaches 0x80000000, wraps to INT_MIN, is sign-extended by movslq\nand turned into a ~16 GiB negative offset from stab->sks, pointing far\nbelow the allocation.\n\nThe faulting access is an xchg() write in sock_map_free().  Without\nKASAN, the same out-of-bounds write can fault on an unmapped vmalloc page\nor corrupt an unrelated allocation if that vmalloc address is populated.\nOn a KASAN kernel with CONFIG_KASAN_VMALLOC=y, the shadow check for that\naddress hits an unmapped shadow page and oopses first:\n\n  BUG: unable to handle page fault for address: fffff521b59c5a00\n  RIP: 0010:kasan_check_range+0x107/0x190\n  Call Trace:\n   sock_map_free+0x93/0x190\n   map_create+0x68d/0xb30\n   __sys_bpf+0x21e/0x2e70\n\nVmcore confirmed stab->map.max_entries == 0xffffffff, stab->sks ==\n0xffffc911ace2d000, and the faulting address sks + (s64)INT_MIN * 8\nexactly at 0xffffc90dace2d000.  The same buggy path is reached on the\nnormal close()/bpf_map_free_deferred() path whenever such a map is\ndestroyed.\n\nsock_map_alloc() used to bound its allocation size through\nbpf_map_charge_init(), but the bound was dropped when rlimit-based memory\naccounting was removed.  Reject max_entries > INT_MAX at creation time so\nthe signed iterator in sock_map_free() never sees a value that would\noverflow.\n\nTriggered by syzkaller and reproduced on both a 6.6-based KASAN kernel\nand the upstream v7.3-rc2 kernel.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98588"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/814a81c842bd88f6bd8a4ce550d560df071a5d03"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/909f761868fda329dc69130ef9eb5b5795bcdf00"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ba7d627dbc67d62df2fa66d7b41e743c3ace0ec8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c56191af3a578b9cc265fa3bd5fc0752c59c1781"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cc70972ddbf0e3398f2f32624d31db78594d50d8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cea597519b9ca6d691c98d92460ead8ece2a07af"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f4a73f49e256bd835368504462be3b57b03febff"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:11Z"
  }
}