Live › vulnerability › CVE-2026-98603
Go to dashboardThe Linux kernel's ovpn driver clears a peer's remembered local source address in place while concurrent transmit paths read it without a lock, so an IPv6 reader can see a torn address. The sources do not state a confirmed attacker outcome.
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 a Linux kernel with the ovpn (OpenVPN data channel offload) module, particularly peers using UDP with IPv6 where the remembered source address becomes unusable. Hosts without the ovpn module loaded are not affected. The sources do not give further detail.
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 clearing stale local source
The UDP output fallback clears bind->local in place when the remembered source address is no longer usable. The bind is RCU-published and read locklessly by concurrent TX, so an IPv6 reader can observe a torn address.
Retry the route lookup with source address autoselection without modifying the bind. After a successful lookup, revalidate the bind and route key under peer->lock, reset the dst cache, and best-effort publish a replacement bind with a wildcard local address.
Do not cache the resolved dst when clearing the local source. Replacing the source invalidates all per-CPU cache entries, while dst_cache_set_ip4 and dst_cache_set_ip6 update only the current CPU slot. The current packet can still use the resolved route; if bind allocation fails, a later cache miss retries the repair.
This page as .md · .json · in your agent: get_signal("CVE-2026-98603")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.