Live › vulnerability › CVE-2026-98604
Go to dashboardThe ovpn driver in the Linux kernel updated a peer's local endpoint address in place without the RCU publish that UDP transmit paths rely on. A concurrent IPv6 update could let a reader see a half-written address, which can misdirect or corrupt traffic.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running the Linux kernel with the ovpn (OpenVPN data-channel offload) module loaded and in use, where peers are configured with IPv6 endpoints. Systems without the ovpn module, or that do not use it, are unlikely to be exposed. The sources do not describe the attacker's position.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
ovpn: replace bind when learning local endpoint
struct ovpn_bind is published through peer->bind with RCU, but local endpoint learning updates bind->local in place under peer->lock. UDP TX reads the field without that lock. In particular, a concurrent IPv6 update can therefore result in a torn address read.
Use ovpn_peer_reset_sockaddr to publish a replacement bind when learning a new local endpoint, just as a remote endpoint change does. Preserve the current remote address and reset the dst cache only after the new bind has been published successfully.
Track remote endpoint changes separately so that float notification and transport-address rehashing remain limited to actual peer floats.
This page as .md · .json · in your agent: get_signal("CVE-2026-98604")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.