CVE-2025-38721

netfilter: ctnetlink: fix refcount leak on table dump

State
Published
Severity
Not scored
Published
Sep 4, 2025
Updated
Oct 15, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before 586892e341fbf698e7cbaca293e1353957db725aAffected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before 962518c6ca9f9a13df099cafa429f72f68ad61f0Affected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before 19b909a4b1452fb97e477d2f08b97f8d04095619Affected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before 41462f4cfc583513833f87f9ee55d12da651a7e3Affected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before 30cf811058552b8cd0e98dff677ef3f89d6d34ceAffected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before a2cb4df7872de069f809de2f076ec8e54d649fe3Affected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before e14f72aa66c029db106921d621edcedef68e065bAffected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before a62d6aa3f31f216b637a4c71b7a8bfc7c57f049bAffected
  • d205dc40798d97d63ad348bfaf7394f445d152d4 to before de788b2e6227462b6dcd0e07474e72c089008f74Affected
LinuxLinux
  • 2.6.18Affected
  • before 2.6.18Not affected
  • 5.4.297 through 5.4.*Not affected
  • 5.10.241 through 5.10.*Not affected
  • 5.15.190 through 5.15.*Not affected
  • 6.1.149 through 6.1.*Not affected
  • 6.6.103 through 6.6.*Not affected
  • 6.12.43 through 6.12.*Not affected
  • 6.15.11 through 6.15.*Not affected
  • 6.16.2 through 6.16.*Not affected
  • 6.17 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.