CVE-2023-53716
Description
In the Linux kernel, the following vulnerability has been resolved:
net: fix skb leak in __skb_tstamp_tx()
Commit 50749f2dd685 ("tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.") added a call to skb_orphan_frags_rx() to fix leaks with zerocopy skbs. But it ended up adding a leak of its own. When skb_orphan_frags_rx() fails, the function just returns, leaking the skb it just cloned. Free it before returning.
This bug was discovered and resolved using Coverity Static Analysis Security Testing (SAST) by Synopsys, Inc.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A memory leak in the Linux kernel's __skb_tstamp_tx() function, introduced by a previous fix, can cause resource exhaustion.
Vulnerability
Analysis
A memory leak vulnerability exists in the Linux kernel's __skb_tstamp_tx() function. The issue was introduced by commit 50749f2dd685, which added a call to skb_orphan_frags_rx() to fix a separate memory leak involving zerocopy skbs and TX timestamps. However, when skb_orphan_frags_rx() fails, the function returns without freeing the skb it had just cloned, resulting in a new leak [1][2][3].
Exploitation
An attacker would need to trigger the specific code path where skb_orphan_frags_rx() fails. This could potentially be achieved by sending network packets that cause the kernel to allocate and timestamp-related skbs, leading to repeated failures. The attack does not require special privileges beyond the ability to send network traffic, but the exact prerequisites depend on the system configuration and kernel version.
Impact
Successful exploitation leads to a kernel memory leak, which can gradually exhaust system memory resources. This may cause denial of service (DoS) as the system becomes unresponsive or crashes due to memory exhaustion. The vulnerability does not directly allow code execution or privilege escalation.
Mitigation
The fix
The fix is included in Linux kernel stable updates. Patched versions are available in the kernel git repository [1][2][3]. Users should update their kernel to a version containing the commit that frees the skb before returning on error. No workaround is known.
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
1Patches
882501f1ead5577933244710858766252f6b2a594382ec6d0e06841a2abf9cc18b4685910f4d928c002548a02fb71d719Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/58766252f6b2c0487cda6976a53d2bb03ae28e2anvd
- git.kernel.org/stable/c/779332447108545ef04682ea29af5f85c0202aeenvd
- git.kernel.org/stable/c/82501f1ead557cbee1c2467654ec109a80334d22nvd
- git.kernel.org/stable/c/8a02fb71d7192ff1a9a47c9d937624966c6e09afnvd
- git.kernel.org/stable/c/a594382ec6d0cc8cff5a8bc7e61b54e3858fb243nvd
- git.kernel.org/stable/c/cc18b4685910d5d9de8314bae9c55790701b1811nvd
- git.kernel.org/stable/c/e06841a2abf9c82735cee39e88b1d79464088840nvd
- git.kernel.org/stable/c/f4d928c00254cfc9dd0ee7076f4a59bceec675f4nvd
News mentions
0No linked articles in our index yet.