net: fix skb leak in __skb_tstamp_tx()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.3, 4.14.316, 4.19.284, 5.4.244, 5.10.181, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6.2.15 · fixed in 6.3
- Linux Linux
From 4.14.315 · fixed in 4.14.316; From 4.19.283 · fixed in 4.19.284; From 5.4.243 · fixed in 5.4.244; From 5.10.180 · fixed in 5.10.181; From 5.15.111 · fixed in 5.15.114; From 6.1.28 · fixed in 6.1.31; From 6.3.2 · fixed in 6.3.5
References 8
git.kernel.org
- stable/c/82501f1ead557cbee1c2467654ec109a80334d22
- stable/c/779332447108545ef04682ea29af5f85c0202aee
- stable/c/58766252f6b2c0487cda6976a53d2bb03ae28e2a
- stable/c/a594382ec6d0cc8cff5a8bc7e61b54e3858fb243
- stable/c/e06841a2abf9c82735cee39e88b1d79464088840
- stable/c/cc18b4685910d5d9de8314bae9c55790701b1811
- stable/c/f4d928c00254cfc9dd0ee7076f4a59bceec675f4
- stable/c/8a02fb71d7192ff1a9a47c9d937624966c6e09af