CVE-2026-98811: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-8rvg-cc82-cvp9
Published
Advisory Summary

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

CVE Identifier CVE-2026-98811
GHSA Identifier GHSA-8rvg-cc82-cvp9
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-98811

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-98811, 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: net/sched: cls_api: reclaim an empty proto on the error path Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down. Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them. This is a follow-up to commit d4e359b3608a ("net/sched: cls_api: fix teardown of an adopted proto on insert-race loss"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place. Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1 flower skip_sw ... action drop` (both fail in fl_hw_replace_filter after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible as a bare `filter protocol ip pref 1 flower chain 0` header in `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)

References

Frequently Asked Questions

What is CVE-2026-98811?
CVE-2026-98811 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-98811?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98811?
CVE-2026-98811 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98811?
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-8rvg-cc82-cvp9",
  "modified" : "2026-10-18T18:32:04Z",
  "published" : "2026-10-18T18:32:04Z",
  "aliases" : [ "CVE-2026-98811" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_api: reclaim an empty proto on the error path\n\nTwo racing tc filter add requests on the same chain/prio of an\nunlocked classifier both run change() on the shared proto and both\ncan fail: the winner's tcf_chain_tp_delete_empty() attempt gives up\nbecause the loser's handle is still in the idr, and the loser's\nerror path drops only its own reference without a second reclamation\nattempt. The empty proto stays linked in the chain, holding the\nchain reference, a block reference and the classifier module\nreference until the chain or block is torn down.\n\nReclaim the proto on the error path of any failed request that holds\na proto reference. The reclamation is emptiness-gated:\ntcf_chain_tp_delete_empty() unlinks the proto only when\ndelete_empty() admits it is empty, so a live shared proto is never\nunlinked. A proto the request created is reclaimed unconditionally -\nit is the only owner, so marking it for deletion is safe even without\na delete_empty callback. Classifiers without one (the check marks the\nproto unconditionally) are rtnl-serialized, so the raced window this\nguard closes cannot arise for them.\n\nThis is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix\nteardown of an adopted proto on insert-race loss\"), which stopped the\nloser of the insert race from unlinking the winner's live proto but\nleft the empty-proto residual in place.\n\nConditions to recreate:\n- CONFIG_NET_CLS_FLOWER=y; veth pair\n- tc qdisc add dev veth0 ingress\n- two concurrent `tc filter add dev veth0 ingress protocol ip pref 1\n  flower skip_sw ... action drop` (both fail in fl_hw_replace_filter\n  after publishing their handle in the idr); repeat in a loop\n- an empty flower tp stays linked after both requests fail; visible\n  as a bare `filter protocol ip pref 1 flower chain 0` header in\n  `tc filter show` with no filter entries\n- CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98811"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0bb8eab29b55045281a4963d4557f2776cdf8cfa"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/315e4fe65cf02ef052de5e6298c3088e448b7517"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/570141625d212fbbcffb9665cb45c0f04610e61a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ebc9611ab154c0cd9f1320e2a73f5e936d7535a9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:35Z"
  }
}