CVE-2026-64043: ovpn: fix race between deleting interface and adding new peer
In the Linux kernel, the following vulnerability has been resolved:
ovpn: fix race between deleting interface and adding new peer
While deleting an existing ovpn interface, there is a very
narrow window where adding a new peer via netlink may cause
the netdevice to hang and prevent its unregistration.
It may happen during ovpn_dellink(), when all existing peers are
freed and the device is queued for deregistration, but a
CMD_PEER_NEW message comes in adding a new peer that takes again
a reference to the netdev.
At this point there is no way to release the device because we are
under the assumption that all peers were already released.
Fix the race condition by releasing all peers in ndo_uninit(),
when the netdevice has already been removed from the netdev
list.
Also ovpn_peer_add() has now an extra check that forces the
function to bail out if the device reg_state is not REGISTERED.
This way any incoming CMD_PEER_NEW racing with the interface
deletion routine will simply stop before adding the peer.
Note that the above check happens while holding the netdev_lock
to prevent racing netdev state changes.
ovpn_dellink() is now empty and can be removed.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel race condition in the ovpn interface lifecycle. If a peer is added while an ovpn interface is being deleted, the network device can hang and fail to unregister. The main business risk shown by the sources is local service instability, not confirmed remote compromise.
Executive priority
Treat as a targeted availability issue until vendor severity data improves. Prioritize systems that depend on ovpn for production connectivity, then fold remediation into normal kernel patch cycles.
Technical view
During ovpn_dellink(), existing peers were freed before deregistration. A racing CMD_PEER_NEW netlink request could add a peer and take a new netdev reference, leaving no release path. The fix moves peer release to ndo_uninit() and blocks peer addition unless the netdevice reg_state is REGISTERED under netdev_lock.
Likely exposure
Exposure appears limited to Linux systems using the kernel ovpn driver and affected kernel versions listed in the CVE source. The sources do not identify specific distributions, appliances, or default configurations.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The sources describe a narrow race involving interface deletion and peer creation via netlink, but do not state required privileges or attack path.
Researcher notes
The evidence supports a race-condition availability flaw in ovpn netdevice teardown. Missing details include CVSS, CWE, privilege requirements, distro impact, and exploitability beyond the described race. Do not assume remote exploitability from the provided record.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Check Linux distribution advisories for backported fixes and affected package versions.
Restrict ovpn interface administration to trusted operators only.
Review systems using ovpn before general Linux fleet prioritization.
Validation and detection
Inventory hosts running affected Linux kernel versions from the CVE record.
Confirm whether the ovpn kernel driver is present and in use.
Map installed kernels to distro advisories or the referenced stable commits.
Monitor for ovpn interface deletion failures or stuck network devices.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-64043 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jul 19, 2026, 15:39 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.