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-2025-68245net: netpoll: fix incorrect refcount handling causing incorrect cleanup

Description

In the Linux kernel, the following vulnerability has been resolved: net: netpoll: fix incorrect refcount handling causing incorrect cleanup commit efa95b01da18 ("netpoll: fix use after free") incorrectly ignored the refcount and prematurely set dev->npinfo to NULL during netpoll cleanup, leading to improper behavior and memory leaks. Scenario causing lack of proper cleanup: 1) A netpoll is associated with a NIC (e.g., eth0) and netdev->npinfo is allocated, and refcnt = 1 - Keep in mind that npinfo is shared among all netpoll instances. In this case, there is just one. 2) Another netpoll is also associated with the same NIC and npinfo->refcnt += 1. - Now dev->npinfo->refcnt = 2; - There is just one npinfo associated to the netdev. 3) When the first netpolls goes to clean up: - The first cleanup succeeds and clears np->dev->npinfo, ignoring refcnt. - It basically calls `RCU_INIT_POINTER(np->dev->npinfo, NULL);` - Set dev->npinfo = NULL, without proper cleanup - No ->ndo_netpoll_cleanup() is either called 4) Now the second target tries to clean up - The second cleanup fails because np->dev->npinfo is already NULL. * In this case, ops->ndo_netpoll_cleanup() was never called, and the skb pool is not cleaned as well (for the second netpoll instance) - This leaks npinfo and skbpool skbs, which is clearly reported by kmemleak. Revert commit efa95b01da18 ("netpoll: fix use after free") and adds clarifying comments emphasizing that npinfo cleanup should only happen once the refcount reaches zero, ensuring stable and correct netpoll behavior.

Timeline

  1. ID reserved

    By Linux

  2. 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < 8e6a50edad11e3e1426e4c29e7aa6201f3468ac2
    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < 9b0bb18b4b9dc017c1825a2c5e763615e34a1593
    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < 890472d6fbf062e6de7fdd56642cb305ab79d669
    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < 4afd4ebbad52aa146838ec23082ba393e426a2bb
    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < c645693180a98606c430825223d2029315d85e9d
    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < c79a6d9da29219616b118a3adce9a14cd30f9bd0
    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < 9a51b5ccd1c79afec1c03a4e1e6688da52597556
    • affected efa95b01da18ad22af62f6d99a3243f3be8fd264 – < 49c8d2c1f94cc2f4d1a108530d7ba52614b874c2
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.4.302 – ≤ 5.4.*
    • unaffected 5.10.247 – ≤ 5.10.*
    • unaffected 5.15.197 – ≤ 5.15.*
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.117 – ≤ 6.6.*
    • unaffected 6.12.59 – ≤ 6.12.*
    • unaffected 6.17.9 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .