net: fix skb leak in __skb_tstamp_tx()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cb52e7f24c1d01a536a847dff0d1d95889cc3b5c · < cc18b4685910d5d9de8314bae9c55790701b1811| No fix yet |
| Linux Linux |
| No fix yet |
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.
From the CVE record · Linux
The Linux kernel leaks a cloned skb when skb_orphan_frags_rx() fails in __skb_tstamp_tx(). The input does not establish whether an attacker can trigger the failure or specify any access or user-interaction requirements.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified.