Answer in brief
CVE-2026-98603 records a Unknown severity vulnerability in ovpn: replace bind when clearing stale local source. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=08857b5ec5d91d83e69e40a36554a8c7557b7301 <c44a04722f7dae9a45a101b8e100931ab59f1c18 || >=08857b5ec5d91d83e69e40a36554a8c7557b7301 <72bd1bea37ea2c8553938f086bf48ccd2147dfe1 || >=08857b5ec5d91d83e69e40a36554a8c7557b7301 <7d8104988f423572df1f3347ce578037b1043f34 | c44a04722f7dae9a45a101b8e100931ab59f1c18, 72bd1bea37ea2c8553938f086bf48ccd2147dfe1, 7d8104988f423572df1f3347ce578037b1043f34 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.