CVE-2025-68245

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

December 16, 2025

Last Modified

April 15, 2026

References (8)

Related CVEs

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(4)

What is CVE-2025-68245?
CVE-2025-68245 is a publicly disclosed vulnerability published on December 16, 2025. 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…
When was CVE-2025-68245 disclosed?
CVE-2025-68245 was first published in the National Vulnerability Database on December 16, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68245 actively exploited?
CVE-2025-68245 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 89.7% of all scored CVEs.
How do I remediate CVE-2025-68245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68245, 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

Explore the affected products and dependency analysis for CVE-2025-68245

Explore →

Is Your Infrastructure Affected by CVE-2025-68245?

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

Start Free Scan →Browse All CVEs