CVE-2026-45917

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (4)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

ipvs: do not keep dest_dst if dev is going down - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bae53b3baf2ff2f45f9205c438818fc055601a54
generic

ipvs: do not keep dest_dst if dev is going down - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fde939b0206afc1d5846217a01a16b9bc8c7896
generic

ipvs: do not keep dest_dst if dev is going down - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64af43033503458c46023e56d6ae7bb0f824b55f
generic

ipvs: do not keep dest_dst if dev is going down - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/024eb0bd19f507e6e7f0c7a7e5506d66b5dc1d3e

Vendor Advisories for CVE-2026-45917(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (100 versions)6.18.14-1

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 5× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 190 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 05:43 UTCEG score recompute
  11. 2026-08-25 05:43 UTCVendor advisory
  12. 2026-08-25 05:43 UTCGHSA enrichment
  13. 2026-08-23 15:30 UTCEG score recompute
  14. 2026-08-23 15:30 UTCVendor advisory
  15. 2026-08-23 15:29 UTCGHSA enrichment
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 20:52 UTCEG score recompute
  18. 2026-08-21 20:52 UTCVendor advisory
  19. 2026-08-21 20:52 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 17:41 UTCEG score recompute
  22. 2026-08-20 17:41 UTCVendor advisory
  23. 2026-08-20 17:40 UTCGHSA enrichment
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 09:21 UTCEG score recompute
  2. 2026-08-17 09:21 UTCVendor advisory
  3. 2026-08-17 09:21 UTCGHSA enrichment
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:54 UTCEG score recompute
  6. 2026-08-16 02:54 UTCVendor advisory
  7. 2026-08-16 02:54 UTCGHSA enrichment
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:36 UTCEG score recompute
  10. 2026-08-15 01:36 UTCVendor advisory
  11. 2026-08-15 01:36 UTCGHSA enrichment
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 01:34 UTCEG score recompute
  14. 2026-08-14 01:34 UTCVendor advisory
  15. 2026-08-14 01:34 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 00:30 UTCEG score recompute
  18. 2026-08-13 00:30 UTCVendor advisory
  19. 2026-08-13 00:30 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-12 00:27 UTCEG score recompute
  22. 2026-08-12 00:27 UTCVendor advisory
  23. 2026-08-12 00:27 UTCGHSA enrichment
  24. 2026-08-11 00:15 UTCEG score recompute
  25. 2026-08-11 00:15 UTCVendor advisory
  26. 2026-08-11 00:15 UTCGHSA enrichment
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-09 21:57 UTCEG score recompute
  29. 2026-08-09 21:57 UTCVendor advisory
  30. 2026-08-09 21:57 UTCGHSA enrichment
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-08 21:54 UTCEG score recompute
  33. 2026-08-08 21:54 UTCVendor advisory
  34. 2026-08-08 21:54 UTCGHSA enrichment
  35. 2026-08-08 16:37 UTCEPSS rescore
  36. 2026-08-07 21:01 UTCVendor advisory
  37. 2026-08-07 21:01 UTCGHSA enrichment
  38. 2026-08-06 20:58 UTCEG score recompute
  39. 2026-08-06 20:58 UTCVendor advisory
  40. 2026-08-06 20:58 UTCGHSA enrichment
  41. 2026-08-06 13:47 UTCEPSS rescore
  42. 2026-08-05 20:55 UTCEG score recompute
  43. 2026-08-05 20:55 UTCVendor advisory
  44. 2026-08-05 20:55 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:39 UTCEPSS rescore
  48. 2026-08-03 16:29 UTCEG score recompute
  49. 2026-08-03 16:29 UTCVendor advisory
  50. 2026-08-03 16:29 UTCGHSA enrichment
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 15:45 UTCEG score recompute
  53. 2026-08-02 15:45 UTCVendor advisory
  54. 2026-08-02 15:45 UTCGHSA enrichment
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 15:42 UTCEG score recompute
  57. 2026-08-01 15:42 UTCVendor advisory
  58. 2026-08-01 15:42 UTCGHSA enrichment
  59. 2026-08-01 04:16 UTCEPSS rescore
  60. 2026-07-31 08:03 UTCEG score recompute
  61. 2026-07-31 08:03 UTCGHSA enrichment
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-29 15:51 UTCEG score recompute
  65. 2026-07-29 15:51 UTCGHSA enrichment
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-27 14:13 UTCEPSS rescore
  68. 2026-07-27 12:09 UTCEG score recompute
  69. 2026-07-27 12:09 UTCGHSA enrichment
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 06:12 UTCOSV refresh
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-24 14:17 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-45917?
CVE-2026-45917 is a medium vulnerability published on May 27, 2026. 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 ipvsdst_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…
When was CVE-2026-45917 disclosed?
CVE-2026-45917 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45917 actively exploited?
CVE-2026-45917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-45917?
CVE-2026-45917 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45917, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45917

Explore →

Is Your Infrastructure Affected by CVE-2026-45917?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.