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()… (CVE-2026-74727)
A vulnerability in the Linux kernel's ovpn (OpenVPN) subsystem allowed a race condition where a peer that was removed could be reinserted into internal hash tables, leading to use-after-free (UAF) conditions. This occurred due to a timing window between peer lookup and locking, enabling concurrent removal and rehashing operations to conflict. The issue has been resolved by adding a check to skip rehashing peers already removed from the hash tables.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's ovpn subsystem involved a race condition in ovpn_nl_peer_set_doit() where a peer was looked up before acquiring a lock. Concurrent operations such as peer deletion or socket teardown could remove the peer from hash tables before the lock was acquired, but the code would then rehash the removed peer, effectively resurrecting it in the hash tables. This led to a use-after-free window when the peer was freed but hash entries remained linked. The fix adds a check under lock to bail out of rehashing if the peer's hash entry has already been unhashed, preventing resurrection and UAF.
Potential Impact
The vulnerability could cause use-after-free conditions in the kernel's ovpn peer management, potentially leading to memory corruption or instability. Userspace would believe the peer was removed, but it could still be reachable internally, causing inconsistent state and possible security risks. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding a check to skip rehashing peers already removed from hash tables. Users should update to a kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel patch or upgrading to a fixed kernel release is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or kernel mailing list advisories for the exact fixed versions and patch availability.
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()… (CVE-2026-74727)
Description
A vulnerability in the Linux kernel's ovpn (OpenVPN) subsystem allowed a race condition where a peer that was removed could be reinserted into internal hash tables, leading to use-after-free (UAF) conditions. This occurred due to a timing window between peer lookup and locking, enabling concurrent removal and rehashing operations to conflict. The issue has been resolved by adding a check to skip rehashing peers already removed from the hash tables.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's ovpn subsystem involved a race condition in ovpn_nl_peer_set_doit() where a peer was looked up before acquiring a lock. Concurrent operations such as peer deletion or socket teardown could remove the peer from hash tables before the lock was acquired, but the code would then rehash the removed peer, effectively resurrecting it in the hash tables. This led to a use-after-free window when the peer was freed but hash entries remained linked. The fix adds a check under lock to bail out of rehashing if the peer's hash entry has already been unhashed, preventing resurrection and UAF.
Potential Impact
The vulnerability could cause use-after-free conditions in the kernel's ovpn peer management, potentially leading to memory corruption or instability. Userspace would believe the peer was removed, but it could still be reachable internally, causing inconsistent state and possible security risks. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding a check to skip rehashing peers already removed from hash tables. Users should update to a kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel patch or upgrading to a fixed kernel release is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor or kernel mailing list advisories for the exact fixed versions and patch availability.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vxqr-379f-fhc4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74727"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f0acd9273b499bc6c5
Added to database: 08/22/2026, 22:51:28 UTC
Last enriched: 08/23/2026, 00:55:36 UTC
Last updated: 08/23/2026, 02:52:03 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.