FKIE_CVE-2026-64045

Vulnerability from fkie_nvd - Published: 2026-07-19 16:17 - Updated: 2026-07-20 15:17
Severity
8.4 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
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
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/775d8d7ad02aa345e1588424a6a8b9ae49fb9012
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d3ef441907fca7c340979e577a3db3bb634bf166
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/e5460eb7238c19d651a9b22b2378b587033a4095
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ovpn/tcp.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "e5460eb7238c19d651a9b22b2378b587033a4095",
              "status": "affected",
              "version": "11851cbd60ea1e5abbd97619d69845ead99303d6",
              "versionType": "git"
            },
            {
              "lessThan": "d3ef441907fca7c340979e577a3db3bb634bf166",
              "status": "affected",
              "version": "11851cbd60ea1e5abbd97619d69845ead99303d6",
              "versionType": "git"
            },
            {
              "lessThan": "775d8d7ad02aa345e1588424a6a8b9ae49fb9012",
              "status": "affected",
              "version": "11851cbd60ea1e5abbd97619d69845ead99303d6",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ovpn/tcp.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "lessThan": "6.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.34",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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-\u003epeer, caches the peer\npointer in a local, and drops the read lock. It then passes sock-\u003epeer\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-\u003eclose() without taking lock_sock first.\n\novpn_socket_release() can therefore complete its kref_put -\u003e detach -\u003e\nsynchronize_rcu -\u003e kfree(sock) sequence concurrently, in the window\nafter ovpn_tcp_close() drops rcu_read_lock() but before it dereferences\nsock-\u003epeer. 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\u0027t 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-\u003epeer exactly once into the cached\npeer local, and route all subsequent uses (the hold check, the\novpn_peer_del() call, and the prot-\u003eclose() invocation) through that\nlocal. sock-\u003epeer 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."
    }
  ],
  "id": "CVE-2026-64045",
  "lastModified": "2026-07-20T15:17:05.177",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 8.4,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.5,
        "impactScore": 5.9,
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-07-19T16:17:44.803",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/775d8d7ad02aa345e1588424a6a8b9ae49fb9012"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/d3ef441907fca7c340979e577a3db3bb634bf166"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/e5460eb7238c19d651a9b22b2378b587033a4095"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.