CVE-2025-39764
Description
In the Linux kernel, the following vulnerability has been resolved:
netfilter: ctnetlink: remove refcounting in expectation dumpers
Same pattern as previous patch: do not keep the expectation object alive via refcount, only store a cookie value and then use that as the skip hint for dump resumption.
AFAICS this has the same issue as the one resolved in the conntrack dumper, when we do if (!refcount_inc_not_zero(&exp->use))
to increment the refcount, there is a chance that exp == last, which causes a double-increment of the refcount and subsequent memory leak.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A use-after-free and double-refcount bug in Linux kernel's netfilter ctnetlink expectation dumpers could lead to memory leak.
Vulnerability
Overview
CVE-2025-39764 is a reference counting flaw in the Linux kernel's netfilter connection tracking (ctnetlink) subsystem, specifically in the expectation dump routines. The commit message explains that the code attempted to keep expectation objects alive via an extra refcount increment, but the logic was flawed: when refcount_inc_not_zero is called on the last dumped expectation (exp == last), the refcount is incremented twice, leading to a double-increment and a subsequent memory leak [1][2]. This mirrors a similar issue previously fixed in the conntrack dumper.
Attack
Vector and Exploitation
To exploit this vulnerability, an attacker would need local access to the system and the ability to trigger netlink dumps of conntrack expectations (typically via tools like conntrack -E expect or a custom netlink client). The bug is triggered during dump resumption, where a "cookie" value is used to skip already-dumped entries. No special privileges beyond the ability to read netlink conntrack information (often granted to unprivileged containers or user namespaces) are required [1].
Impact
An attacker can cause a memory leak by repeatedly triggering ctnetlink expectation dumps in a pattern that hits the double-refcount condition. Over time, this leaks kernel memory, potentially leading to denial of service (system instability or resource exhaustion). The CVSS v3 score is 5.5 (Medium), reflecting the local access requirement and the denial-of-service impact [2]. There is no indication of code execution or privilege escalation.
Mitigation
The fix has been merged into the Linux kernel stable tree via commits 078d33c95bf5, b05500444b8eb, and 9e5021a90653 [1][2][3]. Users should update to a kernel version containing these patches. No workaround is available other than restricting local access to the system.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
3Patches
564b7684042249e5021a90653078d33c95bf5a4d634ded4d31492e3dcb2beVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- git.kernel.org/stable/c/1492e3dcb2be3aa46d1963da96aa9593e4e4db5anvdPatch
- git.kernel.org/stable/c/a4d634ded4d3d400f115d84f654f316f249531c9nvdPatch
- git.kernel.org/stable/c/078d33c95bf534d37aa04269d1ae6158e20082d5nvd
- git.kernel.org/stable/c/64b7684042246e3238464c66894e30ba30c7e851nvd
- git.kernel.org/stable/c/9e5021a906532ca16e2aac69c0607711e1c70b1fnvd
- git.kernel.org/stable/c/b05500444b8eb97644efdd180839a04a706be97cnvd
- git.kernel.org/stable/c/bada48ad5b0590e318d0f79636ff62a2ef9f4955nvd
News mentions
0No linked articles in our index yet.