CVE-2026-64045: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-xr5j-v9xh-823c
Share
CVSS 8.4
CWE-476
Published
Advisory Summary

CVE-2026-64045 is a HIGH (CVSS 8.4) security vulnerability vulnerability (CWE-476: NULL Pointer Dereference) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product dereferences a pointer that it expects to be valid but is null.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-64045 at a Glance

CVE Identifier CVE-2026-64045
GHSA Identifier GHSA-xr5j-v9xh-823c
Severity HIGH
CVSS v3.1 Base Score 8.4
CWE Classification CWE-476: NULL Pointer Dereference
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-64045

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-64045, 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 CWE-476: NULL Pointer Dereference, where the product dereferences a pointer that it expects to be valid but is null. 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: ovpn: tcp - use cached peer pointer in ovpn_tcp_close() ovpn_tcp_close() loads the ovpn_socket via rcu_dereference_sk_user_data() under rcu_read_lock(), takes a reference on sock->peer, caches the peer pointer in a local, and drops the read lock. It then passes sock->peer (rather than the cached local) to ovpn_peer_del(), re-dereferencing the ovpn_socket after the RCU read section has ended. Unlike ovpn_tcp_sendmsg(), which uses the same "load under RCU, use after unlock" pattern but is protected by lock_sock() held across the function, ovpn_tcp_close() runs without the socket lock: inet_release() invokes sk_prot->close() without taking lock_sock first. ovpn_socket_release() can therefore complete its kref_put -> detach -> synchronize_rcu -> kfree(sock) sequence concurrently, in the window after ovpn_tcp_close() drops rcu_read_lock() but before it dereferences sock->peer. The synchronize_rcu() in ovpn_socket_release() protects readers that use the dereferenced pointer inside the RCU read section, not those that escape the pointer to a local and use it afterwards. A reproducer follows the pattern of commit 94560267d6c4 ("ovpn: tcp - don't deref NULL sk_socket member after tcp_close()"): trigger a peer removal (keepalive expiration or netlink OVPN_CMD_DEL_PEER) at the same moment userspace closes the TCP fd. That commit fixed the detach-side of the same race window; this one fixes the close-side at a different victim. Tighten the entry block to read sock->peer exactly once into the cached peer local, and route all subsequent uses (the hold check, the ovpn_peer_del() call, and the prot->close() invocation) through that local. sock->peer is only ever written once in ovpn_socket_new() under lock_sock(), before rcu_assign_sk_user_data() publishes the ovpn_socket, and is never reassigned afterwards - but the previous multi-read pattern made that invariant implicit rather than explicit. The same multi-read shape exists in ovpn_tcp_recvmsg(), ovpn_tcp_sendmsg(), ovpn_tcp_data_ready() and ovpn_tcp_write_space(); those will be cleaned up via a dedicated helper in a follow-up net-next series.

References

NVD — CVE-2026-64045 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-64045
git.kernel.org/stable/c/775d8d7ad0... WEB
https://git.kernel.org/stable/c/775d8d7ad02aa345e1588424a6a8b9ae49fb9012
git.kernel.org/stable/c/d3ef441907... WEB
https://git.kernel.org/stable/c/d3ef441907fca7c340979e577a3db3bb634bf166
git.kernel.org/stable/c/e5460eb723... WEB
https://git.kernel.org/stable/c/e5460eb7238c19d651a9b22b2378b587033a4095

Frequently Asked Questions

What is CVE-2026-64045?
CVE-2026-64045 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-476: NULL Pointer Dereference.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-64045?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-64045?
CVE-2026-64045 has a CVSS v3.1 base score of 8.4 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-64045?
CVE-2026-64045 is classified under CWE-476: NULL Pointer Dereference (The product dereferences a pointer that it expects to be valid but is NULL.).
How can I check Maven dependencies for CVE-2026-64045?
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-xr5j-v9xh-823c",
  "modified" : "2026-07-20T15:31:57Z",
  "published" : "2026-07-19T18:31:50Z",
  "aliases" : [ "CVE-2026-64045" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\novpn: tcp - use cached peer pointer in ovpn_tcp_close()\n\novpn_tcp_close() loads the ovpn_socket via rcu_dereference_sk_user_data()\nunder rcu_read_lock(), takes a reference on sock->peer, caches the peer\npointer in a local, and drops the read lock. It then passes sock->peer\n(rather than the cached local) to ovpn_peer_del(), re-dereferencing the\novpn_socket after the RCU read section has ended.\n\nUnlike ovpn_tcp_sendmsg(), which uses the same \"load under RCU, use\nafter unlock\" pattern but is protected by lock_sock() held across the\nfunction, ovpn_tcp_close() runs without the socket lock: inet_release()\ninvokes sk_prot->close() without taking lock_sock first.\n\novpn_socket_release() can therefore complete its kref_put -> detach ->\nsynchronize_rcu -> kfree(sock) sequence concurrently, in the window\nafter ovpn_tcp_close() drops rcu_read_lock() but before it dereferences\nsock->peer. The synchronize_rcu() in ovpn_socket_release() protects\nreaders that use the dereferenced pointer inside the RCU read section,\nnot those that escape the pointer to a local and use it afterwards.\n\nA reproducer follows the pattern of commit 94560267d6c4 (\"ovpn: tcp -\ndon't deref NULL sk_socket member after tcp_close()\"): trigger a peer\nremoval (keepalive expiration or netlink OVPN_CMD_DEL_PEER) at the same\nmoment userspace closes the TCP fd. That commit fixed the detach-side\nof the same race window; this one fixes the close-side at a different\nvictim.\n\nTighten the entry block to read sock->peer exactly once into the cached\npeer local, and route all subsequent uses (the hold check, the\novpn_peer_del() call, and the prot->close() invocation) through that\nlocal. sock->peer is only ever written once in ovpn_socket_new() under\nlock_sock(), before rcu_assign_sk_user_data() publishes the ovpn_socket,\nand is never reassigned afterwards - but the previous multi-read pattern\nmade that invariant implicit rather than explicit. The same multi-read\nshape exists in ovpn_tcp_recvmsg(), ovpn_tcp_sendmsg(),\novpn_tcp_data_ready() and ovpn_tcp_write_space(); those will be cleaned\nup via a dedicated helper in a follow-up net-next series.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64045"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/775d8d7ad02aa345e1588424a6a8b9ae49fb9012"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d3ef441907fca7c340979e577a3db3bb634bf166"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e5460eb7238c19d651a9b22b2378b587033a4095"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-476" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-07-19T16:17:44Z"
  }
}