PoC Monitor
← All CVEs
CVE-2026-74727published 22 Aug 2026 15:33 UTCData: JSON · API

Linux

ovpn: skip rehash for peers already removed from by_id

In the Linux kernel, the following vulnerability has been resolved: ovpn: skip rehash for peers already removed from by_id ovpn_nl_peer_set_doit() resolves the target peer via ovpn_peer_get_by_id() before taking ovpn->lock. In the window between the lookup (which only takes a refcount) and the subsequent spin_lock_bh(&ovpn->lock), a concurrent OVPN_CMD_PEER_DEL, keepalive expiry, or socket teardown can take ovpn->lock first, run ovpn_peer_remove() to unhash the peer from all four tables (by_id, by_vpn_addr4/6, by_transp_addr) and release the lock. set_doit then acquires ovpn->lock and calls ovpn_peer_hash_vpn_ip(), which re-inserts the now-removed peer back into the rehashing tables. The same race affects the float path: ovpn_peer_endpoints_update() holds only a refcount and acquires ovpn->lock very late (after async AEAD decrypt and a netlink notification), then rehashes the peer in the by_transp_addr table. The resurrected peer becomes reachable again from the RX lookup (ovpn_peer_get_by_transp_addr) and the TX VPN-IP lookup, even though userspace believes it is gone. Once the data-path refcount drops the peer is freed via call_rcu while the hash entries embedded in it remain linked, opening a UAF window. Bail out of the rehash when hash_entry_id is unhashed, mirroring the sentinel already used by ovpn_peer_remove() to detect the already-removed state. The check is safe under ovpn->lock, which serializes every mutation of hash_entry_id, and is a no-op for the add path because ovpn_peer_add_mp() inserts hash_entry_id before calling ovpn_peer_hash_vpn_ip().

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.8critical · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 1d36a36f6d5347360ef9681a05f6166683bafd1d, < d20c181088984b6eaa8d7fe7cb5ab3510988df59
  • >= 1d36a36f6d5347360ef9681a05f6166683bafd1d, < 66745480298775f188b2f5ad266643e85a90f73b
  • >= 1d36a36f6d5347360ef9681a05f6166683bafd1d, < 33ec10567fe14456063daf549fdf1a4f53448e4c

Fixed in d20c181088984b6eaa8d7fe7cb5ab3510988df59, 66745480298775f188b2f5ad266643e85a90f73b, 33ec10567fe14456063daf549fdf1a4f53448e4c

Linux Linux
  • 6.16

Fixed in 0, 6.18.45, 7.1.9, 7.2

Mitigation

Upgrade Linux to d20c181088984b6eaa8d7fe7cb5ab3510988df59 or 66745480298775f188b2f5ad266643e85a90f73b or 33ec10567fe14456063daf549fdf1a4f53448e4c or later.

Upgrade Linux to 0 or 6.18.45 or 7.1.9 or 7.2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published22 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

1 informational

Informational 1
RepositoryCreatedStarsAssessment
Kosifuchs/ovpn-kernel-backport 6 Oct 2026 +45 d 0 Informational · detection
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.