CVE-2026-45917
ipvs: do not keep dest_dst if dev is going down
In the Linux kernel, the following vulnerability has been resolved: ipvs: do not keep dest_dst if dev is going down There is race between the netdev notifier ip_vs_dst_event() and the code that caches dst with dev that is going down. As the FIB can be notified for the closed device after our handler finishes, it is possible valid route to be returned and cached resuling in a leaked dev reference until the dest is not removed. To prevent new dest_dst to be attached to dest just after the handler dropped the old one, add a netif_running() check to make sure the notifier handler is not currently running for device that is closing.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 7a4f0761fce32ff4918a7c23b08db564ad33092d; < 0b60fb44247eab81e7a9490c38ca62c7120eec75 (affected, git) ≥ 7a4f0761fce32ff4918a7c23b08db564ad33092d; < 11d35b11013442576f35fd9e8a8fc16155101906 (affected, git) ≥ 7a4f0761fce32ff4918a7c23b08db564ad33092d; < 64af43033503458c46023e56d6ae7bb0f824b55f (affected, git) ≥ 7a4f0761fce32ff4918a7c23b08db564ad33092d; < bae53b3baf2ff2f45f9205c438818fc055601a54 (affected, git) ≥ 7a4f0761fce32ff4918a7c23b08db564ad33092d; < 024eb0bd19f507e6e7f0c7a7e5506d66b5dc1d3e (affected, git) ≥ 7a4f0761fce32ff4918a7c23b08db564ad33092d; < 8fde939b0206afc1d5846217a01a16b9bc8c7896 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
2.6.39 (affected) ≥ 0; < 2.6.39 (unaffected, semver) ≥ 6.1.191; ≤ 6.1.* (unaffected, semver) ≥ 6.6.160; ≤ 6.6.* (unaffected, semver) ≥ 6.12.75; ≤ 6.12.* (unaffected, semver) ≥ 6.18.14; ≤ 6.18.* (unaffected, semver) ≥ 6.19.4; ≤ 6.19.* (unaffected, semver) ≥ 7.0; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/0b60fb44247eab81e7a9490c38ca62c7120eec75CNA: Linux
- https://git.kernel.org/stable/c/11d35b11013442576f35fd9e8a8fc16155101906CNA: Linux
- https://git.kernel.org/stable/c/64af43033503458c46023e56d6ae7bb0f824b55fCNA: Linux
- https://git.kernel.org/stable/c/bae53b3baf2ff2f45f9205c438818fc055601a54CNA: Linux
- https://git.kernel.org/stable/c/024eb0bd19f507e6e7f0c7a7e5506d66b5dc1d3eCNA: Linux
- https://git.kernel.org/stable/c/8fde939b0206afc1d5846217a01a16b9bc8c7896CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.