CVE-2023-53716

net: fix skb leak in __skb_tstamp_tx()

N/A
Published: October 22, 2025 at 01:23 PM UTC
Updated: October 28, 2026 at 07:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14.315 ≤ v < 4.14.3164.19.283 ≤ v < 4.19.2845.10.180 ≤ v < 5.10.1815.15.111 ≤ v < 5.15.1145.4.243 ≤ v < 5.4.2446.1.28 ≤ v < 6.1.316.2.15 ≤ v < 6.36.3.2 ≤ v < 6.3.51f69c086b20e27763af28145981435423f088268230a5ed7d813fb516de81d23f09d7506753e41e9281072fb2a7294cde7acbf5375b879f40a8001b730290f210ba7426ff7592fe2eb4114b1b5bad2194.14.3154.19.283426384dd4980040651536fef5feac4dcc4d7ee4e43e4197dd5f6b474a8b16f8b6a42cd45cf4f9d1a5.10.1805.15.1115.4.24350749f2dd6854a41830996ad302aef2ffaf011d86.1.286.2.156.3.2602fa8af44fd55a58f9e94eb673e8adad2c6cc46cb52e7f24c1d01a536a847dff0d1d95889cc3b5c
Vendor states this is fixed in 58766252f6b2c0487cda6976a53d2bb03ae28e2a (fixed)
Vendor states this is fixed in 779332447108545ef04682ea29af5f85c0202aee (fixed)
Vendor states this is fixed in 82501f1ead557cbee1c2467654ec109a80334d22 (fixed)
Vendor states this is fixed in 8a02fb71d7192ff1a9a47c9d937624966c6e09af (fixed)
Vendor states this is fixed in a594382ec6d0cc8cff5a8bc7e61b54e3858fb243 (fixed)
Vendor states this is fixed in cc18b4685910d5d9de8314bae9c55790701b1811 (fixed)
Vendor states this is fixed in e06841a2abf9c82735cee39e88b1d79464088840 (fixed)
Vendor states this is fixed in f4d928c00254cfc9dd0ee7076f4a59bceec675f4 (fixed)
Affected range stops below 4.14.316, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.19.284, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.10.181, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.15.114, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.4.244, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.31, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.3.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card