CVE-2026-90065: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-6c8w-4wvx-63q5
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90065
GHSA Identifier GHSA-6c8w-4wvx-63q5
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-90065

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-90065, 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/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure IPPROTO_SMC sockets create an internal TCP sock ("clcsock") from the proto->init hook. When socket creation fails after proto->init has run - e.g. a cgroup BPF program attached to BPF_CGROUP_INET_SOCK_CREATE denies the socket - sk_common_release() only invokes sk_prot->destroy if it is set, but neither smc_inet_prot nor smc_inet6_prot defines it, and smc_destruct() returns early unless sk_state is SMC_CLOSED. As a result, every failing socket(AF_INET, SOCK_STREAM, IPPROTO_SMC) call leaks one tcp_sock, so an unprivileged task able to attach a deny-all BPF_CGROUP_INET_SOCK_CREATE program to its own cgroup can grow kernel memory unboundedly. Add a .destroy hook to both protos that releases the clcsock via smc_clcsock_release(). smc_sk_init() hashes the sock into the smc hashinfo before the clcsock is created, and smc_diag dumps walk that hash dereferencing smc->clcsock without taking clcsock_release_lock, while sk_common_release() calls .destroy before .unhash. Unhash the sock before releasing the clcsock, as __smc_release() does, so a concurrent dump cannot observe the release; the second unhash in sk_common_release() is a no-op.

References

NVD — CVE-2026-90065 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90065
git.kernel.org/stable/c/2f4ece7fed... WEB
https://git.kernel.org/stable/c/2f4ece7fed6d915ec64b7735962c0d84d6261032
git.kernel.org/stable/c/84180988a4... WEB
https://git.kernel.org/stable/c/84180988a455fd8e147c6b35c8df65d8b8cc76c2
git.kernel.org/stable/c/94a913cd52... WEB
https://git.kernel.org/stable/c/94a913cd521c0f0408820bcdbd80dadf076d97b5
git.kernel.org/stable/c/cec261b0b4... WEB
https://git.kernel.org/stable/c/cec261b0b4c5c0b044165303198d10ffcdf3414c

Frequently Asked Questions

What is CVE-2026-90065?
CVE-2026-90065 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-90065?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90065?
CVE-2026-90065 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90065?
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-6c8w-4wvx-63q5",
  "modified" : "2026-09-17T18:31:49Z",
  "published" : "2026-09-17T18:31:49Z",
  "aliases" : [ "CVE-2026-90065" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure\n\nIPPROTO_SMC sockets create an internal TCP sock (\"clcsock\") from the\nproto->init hook. When socket creation fails after proto->init has\nrun - e.g. a cgroup BPF program attached to BPF_CGROUP_INET_SOCK_CREATE\ndenies the socket - sk_common_release() only invokes sk_prot->destroy\nif it is set, but neither smc_inet_prot nor smc_inet6_prot defines it,\nand smc_destruct() returns early unless sk_state is SMC_CLOSED. As a\nresult, every failing socket(AF_INET, SOCK_STREAM, IPPROTO_SMC) call\nleaks one tcp_sock, so an unprivileged task able to attach a deny-all\nBPF_CGROUP_INET_SOCK_CREATE program to its own cgroup can grow kernel\nmemory unboundedly.\n\nAdd a .destroy hook to both protos that releases the clcsock via\nsmc_clcsock_release(). smc_sk_init() hashes the sock into the smc\nhashinfo before the clcsock is created, and smc_diag dumps walk that\nhash dereferencing smc->clcsock without taking clcsock_release_lock,\nwhile sk_common_release() calls .destroy before .unhash. Unhash the\nsock before releasing the clcsock, as __smc_release() does, so a\nconcurrent dump cannot observe the release; the second unhash in\nsk_common_release() is a no-op.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90065"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2f4ece7fed6d915ec64b7735962c0d84d6261032"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/84180988a455fd8e147c6b35c8df65d8b8cc76c2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/94a913cd521c0f0408820bcdbd80dadf076d97b5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cec261b0b4c5c0b044165303198d10ffcdf3414c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:16:55Z"
  }
}