Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-45917ipvs: do not keep dest_dst if dev is going down

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-45917, by who scored it
Scored byCVSSScoreVector
NVDNVD · Undergoing Analysis3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7a4f0761fce32ff4918a7c23b08db564ad33092d – < 0b60fb44247eab81e7a9490c38ca62c7120eec75
    • affected 7a4f0761fce32ff4918a7c23b08db564ad33092d – < 11d35b11013442576f35fd9e8a8fc16155101906
    • affected 7a4f0761fce32ff4918a7c23b08db564ad33092d – < 64af43033503458c46023e56d6ae7bb0f824b55f
    • affected 7a4f0761fce32ff4918a7c23b08db564ad33092d – < bae53b3baf2ff2f45f9205c438818fc055601a54
    • affected 7a4f0761fce32ff4918a7c23b08db564ad33092d – < 024eb0bd19f507e6e7f0c7a7e5506d66b5dc1d3e
    • affected 7a4f0761fce32ff4918a7c23b08db564ad33092d – < 8fde939b0206afc1d5846217a01a16b9bc8c7896
  • Linux · Linux

    • affected 2.6.39
    • unaffected < 2.6.39
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.14 – ≤ 6.18.*
    • unaffected 6.19.4 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-45917 badge
[![CVE-2026-45917](https://cveledger.app/badge/CVE-2026-45917.svg)](https://cveledger.app/cve/CVE-2026-45917)

Record last updated .