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-38721netfilter: ctnetlink: fix refcount leak on table dump

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 14 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-2025-38721, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.18% · top 93% of all CVEs (19 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 d205dc40798d97d63ad348bfaf7394f445d152d4 – < 586892e341fbf698e7cbaca293e1353957db725a
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < 962518c6ca9f9a13df099cafa429f72f68ad61f0
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < 19b909a4b1452fb97e477d2f08b97f8d04095619
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < 41462f4cfc583513833f87f9ee55d12da651a7e3
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < 30cf811058552b8cd0e98dff677ef3f89d6d34ce
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < a2cb4df7872de069f809de2f076ec8e54d649fe3
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < e14f72aa66c029db106921d621edcedef68e065b
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < a62d6aa3f31f216b637a4c71b7a8bfc7c57f049b
    • affected d205dc40798d97d63ad348bfaf7394f445d152d4 – < de788b2e6227462b6dcd0e07474e72c089008f74
  • Linux · Linux

    • affected 2.6.18
    • unaffected < 2.6.18
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References15

Sources

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

Badge for a README or a ticket

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

Record last updated .