CVE-2026-68342

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

ovpn: avoid putting unrelated P2P peer on socket release

ovpn_peer_release_p2p() is called when an OVPN UDP socket is being

destroyed. It checks the currently published P2P peer and releases it only

if that peer still uses the socket being destroyed.

A peer replacement can publish a new peer before the old UDP socket is

destroyed. When the old socket destruction path runs afterwards,

ovpn_peer_release_p2p() observes the new peer through ovpn->peer. Since the

new peer uses a different socket, the function takes the socket mismatch

branch.

That branch still calls ovpn_peer_put(peer). At this point, however, peer

is the currently published replacement peer, not the peer associated with

the socket being destroyed. Dropping its reference can free it while

ovpn->peer still points to it, leading to later use-after-free accesses

from the peer and socket cleanup paths.

KASAN reports this as a slab-use-after-free on the kma

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References