CVE-2022-48809
Description
In the Linux kernel, the following vulnerability has been resolved: net: fix a memleak when uncloning an skb dst and its metadata When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb. The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak. Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.
How to fix
- linux linux_kernel4.9.302, 4.14.267, 4.19.230, 5.4.180, 5.10.101, 5.15.24, 5.16.10 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | 4.3 ≤ v < 4.9.302, 4.10 ≤ v < 4.14.267, 4.15 ≤ v < 4.19.230, 4.20 ≤ v < 5.4.180, 5.5 ≤ v < 5.10.101, 5.11 ≤ v < 5.15.24, 5.16 ≤ v < 5.16.10 | 4.9.302, 4.14.267, 4.19.230, 5.4.180, 5.10.101, 5.15.24, 5.16.10 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.