GHSA-FVVM-56RX-VQJG
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98603"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:13Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\novpn: replace bind when clearing stale local source\n\nThe UDP output fallback clears bind-\u003elocal in place when the remembered\nsource address is no longer usable. The bind is RCU-published and read\nlocklessly by concurrent TX, so an IPv6 reader can observe a torn\naddress.\n\nRetry the route lookup with source address autoselection without\nmodifying the bind. After a successful lookup, revalidate the bind and\nroute key under peer-\u003elock, reset the dst cache, and best-effort publish\na replacement bind with a wildcard local address.\n\nDo not cache the resolved dst when clearing the local source. Replacing\nthe source invalidates all per-CPU cache entries, while\ndst_cache_set_ip4 and dst_cache_set_ip6 update only the current CPU\nslot. The current packet can still use the resolved route; if bind\nallocation fails, a later cache miss retries the repair.",
"id": "GHSA-fvvm-56rx-vqjg",
"modified": "2026-10-18T18:31:56Z",
"published": "2026-10-18T18:31:56Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98603"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/72bd1bea37ea2c8553938f086bf48ccd2147dfe1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7d8104988f423572df1f3347ce578037b1043f34"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c44a04722f7dae9a45a101b8e100931ab59f1c18"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.