CVE-2026-80850: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-cpgq-xw99-wp3q
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80850
GHSA Identifier GHSA-cpgq-xw99-wp3q
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-80850

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-80850, 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: tcp: fix AO info use-after-free in tcp_ao_connect_init() tcp_v4_connect() adds a SYN-SENT socket to the ehash before calling tcp_connect(). If TCP-AO is configured, tcp_connect() first verifies that a key matches the peer and the bound device's current L3 master. tcp_ao_connect_init() later resolves the L3 master again and removes keys which do not match it. The socket lock does not stabilize the bound device's VRF membership. Detaching the device from its VRF between the initial validation and the L3-master calculation in tcp_ao_connect_init() can therefore make the validation succeed while initialization observes the default L3 domain and removes the only key. The subsequent AO lookup then fails, so the no-key path clears tp->ao_info and frees it directly. The receive path can find the socket in the ehash and load tp->ao_info under RCU before acquiring the socket lock. A reader which loaded the old pointer can thus continue into tcp_inbound_ao_hash() after the direct free. The issue was found during a static audit of TCP-AO object lifetime. An unprivileged reproducer in self-created user and network namespaces raced connect() with detaching a veth from its VRF while sending TCP-AO segments. It triggered the same KASAN report on two fresh boots: BUG: KASAN: slab-use-after-free in tcp_inbound_ao_hash+0x585/0x19f0 Write of size 8 at addr ffff88800bf88128 by task tcp_ao_vrf_race/232 Call Trace: tcp_inbound_ao_hash+0x585/0x19f0 tcp_inbound_hash+0x677/0xa80 tcp_v4_rcv+0x1c3e/0x3ab0 Allocated by task 235: tcp_ao_alloc_info+0x43/0xf0 tcp_ao_add_cmd+0xdf7/0x13b0 do_tcp_setsockopt+0x168c/0x2640 Freed by task 235: kfree+0x1b8/0x550 tcp_connect+0x252/0x4f00 tcp_v4_connect+0x1114/0x1720 The bad address is 40 bytes inside the freed 128-byte object, matching the tcp_ao_info counters.key_not_found field. The two runs used 1000 attempts each, reached the no-key path 366 and 411 times, and produced one and two KASAN reports respectively. With this change, the same reproducer reached the no-key path 366 times in 1000 attempts without a KASAN report or oops. Use tcp_ao_destroy_sock() for the no-key path. It unpublishes the AO info, updates the socket memory and static-key accounting, and defers the free until after an RCU grace period. Also drop the WARN_ON_ONCE() and its stale comment. The VRF detach race makes the no-key state reachable during normal operation, so it is a handled condition rather than an impossible assertion. On panic_on_warn kernels the WARN would turn this handled race into a kernel panic.

References

NVD — CVE-2026-80850 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80850
git.kernel.org/stable/c/284d7fd0ee... WEB
https://git.kernel.org/stable/c/284d7fd0eec8774bd6214921fbf525cf907c590e
git.kernel.org/stable/c/594ba77210... WEB
https://git.kernel.org/stable/c/594ba77210a1f065832211851a2d7e14d11fcbdb
git.kernel.org/stable/c/70051a5778... WEB
https://git.kernel.org/stable/c/70051a57786d5b23f059fbaf5c8241eca14d42ed
git.kernel.org/stable/c/d17e88b6b6... WEB
https://git.kernel.org/stable/c/d17e88b6b60ff4ef64e0dd1444f935cb13dee1cd
git.kernel.org/stable/c/ea30dc5267... WEB
https://git.kernel.org/stable/c/ea30dc5267e367b8a5e1e06cc074f813bcbf18b2

Frequently Asked Questions

What is CVE-2026-80850?
CVE-2026-80850 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-80850?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80850?
CVE-2026-80850 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80850?
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-cpgq-xw99-wp3q",
  "modified" : "2026-09-04T18:31:29Z",
  "published" : "2026-09-04T18:31:29Z",
  "aliases" : [ "CVE-2026-80850" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntcp: fix AO info use-after-free in tcp_ao_connect_init()\n\ntcp_v4_connect() adds a SYN-SENT socket to the ehash before calling\ntcp_connect().  If TCP-AO is configured, tcp_connect() first verifies that\na key matches the peer and the bound device's current L3 master.\ntcp_ao_connect_init() later resolves the L3 master again and removes keys\nwhich do not match it.\n\nThe socket lock does not stabilize the bound device's VRF membership.\nDetaching the device from its VRF between the initial validation and the\nL3-master calculation in tcp_ao_connect_init() can therefore make the\nvalidation succeed while initialization observes the default L3 domain and\nremoves the only key.  The subsequent AO lookup then fails, so the no-key\npath clears tp->ao_info and frees it directly.\n\nThe receive path can find the socket in the ehash and load tp->ao_info\nunder RCU before acquiring the socket lock.  A reader which loaded the old\npointer can thus continue into tcp_inbound_ao_hash() after the direct free.\n\nThe issue was found during a static audit of TCP-AO object lifetime.  An\nunprivileged reproducer in self-created user and network namespaces raced\nconnect() with detaching a veth from its VRF while sending TCP-AO segments.\nIt triggered the same KASAN report on two fresh boots:\n\n  BUG: KASAN: slab-use-after-free in tcp_inbound_ao_hash+0x585/0x19f0\n  Write of size 8 at addr ffff88800bf88128 by task tcp_ao_vrf_race/232\n\n  Call Trace:\n   tcp_inbound_ao_hash+0x585/0x19f0\n   tcp_inbound_hash+0x677/0xa80\n   tcp_v4_rcv+0x1c3e/0x3ab0\n\n  Allocated by task 235:\n   tcp_ao_alloc_info+0x43/0xf0\n   tcp_ao_add_cmd+0xdf7/0x13b0\n   do_tcp_setsockopt+0x168c/0x2640\n\n  Freed by task 235:\n   kfree+0x1b8/0x550\n   tcp_connect+0x252/0x4f00\n   tcp_v4_connect+0x1114/0x1720\n\nThe bad address is 40 bytes inside the freed 128-byte object, matching the\ntcp_ao_info counters.key_not_found field.  The two runs used 1000 attempts\neach, reached the no-key path 366 and 411 times, and produced one and two\nKASAN reports respectively.  With this change, the same reproducer reached\nthe no-key path 366 times in 1000 attempts without a KASAN report or oops.\n\nUse tcp_ao_destroy_sock() for the no-key path.  It unpublishes the AO info,\nupdates the socket memory and static-key accounting, and defers the free\nuntil after an RCU grace period.\n\nAlso drop the WARN_ON_ONCE() and its stale comment.  The VRF detach race\nmakes the no-key state reachable during normal operation, so it is a\nhandled condition rather than an impossible assertion.  On panic_on_warn\nkernels the WARN would turn this handled race into a kernel panic.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80850"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/284d7fd0eec8774bd6214921fbf525cf907c590e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/594ba77210a1f065832211851a2d7e14d11fcbdb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/70051a57786d5b23f059fbaf5c8241eca14d42ed"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d17e88b6b60ff4ef64e0dd1444f935cb13dee1cd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ea30dc5267e367b8a5e1e06cc074f813bcbf18b2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-04T16:18:13Z"
  }
}