CVE-2026-98076: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-hv39-rmvr-p67c
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98076
GHSA Identifier GHSA-hv39-rmvr-p67c
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-98076

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-98076, 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: tracing/probes: Fix use-after-free on field name/type of events with multiple probes The fields of a probe-based dynamic event (kprobe, uprobe, eprobe and fprobe events) are created in traceprobe_define_arg_fields() by handing the probe_arg name/type strings to trace_define_field(), which only stores the pointers without copying. Those strings are owned by the trace_probe and are freed when that probe is removed. An event can have several probes attached. The field list is defined only once, by the first probe that registers the event, but it is kept alive by any surviving sibling probe. Deleting just that first probe by symbol - # primary A: fields are defined from A's args echo 'p:kprobes/ev vfs_read a1=$arg1' > kprobe_events # append B: shares A's event call echo 'p:kprobes/ev vfs_write a1=$arg1' >> kprobe_events # delete only A (matched by symbol), B survives echo '-:kprobes/ev vfs_read' >> kprobe_events frees A's args (trace_probe_cleanup() -> traceprobe_free_probe_arg()), but trace_probe_unlink() keeps the trace_probe_event because the probe list is not empty. The event call stays registered via B while its fields now reference freed memory. Any field lookup then reads it, e.g. echo 'a1 == 1' > events/kprobes/ev/filter BUG: KASAN: slab-use-after-free in strcmp+0xa7/0xb0 Call Trace: strcmp trace_find_event_field parse_pred process_preds create_filter apply_event_filter event_filter_write field->name references parg->name (kstrdup'd, freed with the probe) and, for array arguments, field->type references parg->fmt (kmalloc'd, freed with the probe) - the scalar type otherwise points at the static fmttype rodata, which is safe. Have traceprobe_define_arg_fields() duplicate the name and type strings and anchor the copies on the trace_probe_event, which embeds the event call and outlives every individual probe; trace_probe_event_free() releases them. The reproducer above triggers reliably; the field lookup and the delete both run under event_mutex, so this is a dangling reference after removal rather than a race. The issue was found by the autokbug dynamic kernel fuzzer at Tencent Yunding Lab.

References

NVD — CVE-2026-98076 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98076
git.kernel.org/stable/c/178ff2e011... WEB
https://git.kernel.org/stable/c/178ff2e011e21fbebdf57f5d58a408fe59136d82
git.kernel.org/stable/c/38305e1b8b... WEB
https://git.kernel.org/stable/c/38305e1b8b1ec27eef8f2d4e461e3b6c8624d494
git.kernel.org/stable/c/411c9080a7... WEB
https://git.kernel.org/stable/c/411c9080a776577664531b4f7d3ee53b7a747ba8
git.kernel.org/stable/c/68ae584169... WEB
https://git.kernel.org/stable/c/68ae584169c7a41fc9bc4677c1d368983cf44b21
git.kernel.org/stable/c/6d6118c17b... WEB
https://git.kernel.org/stable/c/6d6118c17bc791594cbfd9cc4936ee21073b894a
git.kernel.org/stable/c/86b7a239ec... WEB
https://git.kernel.org/stable/c/86b7a239ec6b14a7544200ede85474c6f5526049
git.kernel.org/stable/c/9379e19382... WEB
https://git.kernel.org/stable/c/9379e193826f23876daccb3351fab89c87084ba3
git.kernel.org/stable/c/a2510fcaad... WEB
https://git.kernel.org/stable/c/a2510fcaad92b09b34574c97e8356234c6a84a9a

Frequently Asked Questions

What is CVE-2026-98076?
CVE-2026-98076 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-98076?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98076?
CVE-2026-98076 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98076?
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-hv39-rmvr-p67c",
  "modified" : "2026-10-03T12:31:26Z",
  "published" : "2026-09-25T12:31:35Z",
  "aliases" : [ "CVE-2026-98076" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing/probes: Fix use-after-free on field name/type of events with multiple probes\n\nThe fields of a probe-based dynamic event (kprobe, uprobe, eprobe and\nfprobe events) are created in traceprobe_define_arg_fields() by handing\nthe probe_arg name/type strings to trace_define_field(), which only\nstores the pointers without copying. Those strings are owned by the\ntrace_probe and are freed when that probe is removed.\n\nAn event can have several probes attached. The field list is defined\nonly once, by the first probe that registers the event, but it is kept\nalive by any surviving sibling probe. Deleting just that first probe by\nsymbol -\n\n  # primary A: fields are defined from A's args\n  echo 'p:kprobes/ev vfs_read  a1=$arg1' >  kprobe_events\n  # append B: shares A's event call\n  echo 'p:kprobes/ev vfs_write a1=$arg1' >> kprobe_events\n  # delete only A (matched by symbol), B survives\n  echo '-:kprobes/ev vfs_read'           >> kprobe_events\n\nfrees A's args (trace_probe_cleanup() -> traceprobe_free_probe_arg()),\nbut trace_probe_unlink() keeps the trace_probe_event because the probe\nlist is not empty. The event call stays registered via B while its\nfields now reference freed memory. Any field lookup then reads it, e.g.\n\n  echo 'a1 == 1' > events/kprobes/ev/filter\n\n  BUG: KASAN: slab-use-after-free in strcmp+0xa7/0xb0\n  Call Trace:\n   strcmp\n   trace_find_event_field\n   parse_pred\n   process_preds\n   create_filter\n   apply_event_filter\n   event_filter_write\n\nfield->name references parg->name (kstrdup'd, freed with the probe) and,\nfor array arguments, field->type references parg->fmt (kmalloc'd, freed\nwith the probe) - the scalar type otherwise points at the static\nfmttype rodata, which is safe.\n\nHave traceprobe_define_arg_fields() duplicate the name and type strings\nand anchor the copies on the trace_probe_event, which embeds the event\ncall and outlives every individual probe; trace_probe_event_free()\nreleases them.\n\nThe reproducer above triggers reliably; the field lookup and the delete\nboth run under event_mutex, so this is a dangling reference after\nremoval rather than a race.\n\nThe issue was found by the autokbug dynamic kernel fuzzer at Tencent\nYunding Lab.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98076"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/178ff2e011e21fbebdf57f5d58a408fe59136d82"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/38305e1b8b1ec27eef8f2d4e461e3b6c8624d494"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/411c9080a776577664531b4f7d3ee53b7a747ba8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/68ae584169c7a41fc9bc4677c1d368983cf44b21"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6d6118c17bc791594cbfd9cc4936ee21073b894a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/86b7a239ec6b14a7544200ede85474c6f5526049"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9379e193826f23876daccb3351fab89c87084ba3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a2510fcaad92b09b34574c97e8356234c6a84a9a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:36Z"
  }
}