CVE-2022-48809
published 2024-07-16CVE-2022-48809: 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…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.28%
20.4th percentile
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.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.10-1 (bookworm) | linux 5.16.10-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < 4ac84498fbe84a00e7aef185e2bb3e40ce71eca4 | 4ac84498fbe84a00e7aef185e2bb3e40ce71eca4 |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < c1ff27d100e2670b03cbfddb9117e5f9fc672540 | c1ff27d100e2670b03cbfddb9117e5f9fc672540 |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < 0be943916d781df2b652793bb2d3ae4f9624c10a | 0be943916d781df2b652793bb2d3ae4f9624c10a |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < a80817adc2a4c1ba26a7aa5f3ed886e4a18dff88 | a80817adc2a4c1ba26a7aa5f3ed886e4a18dff88 |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < 00e6d6c3bc14dfe32824e2c515f0e0f2d6ecf2f1 | 00e6d6c3bc14dfe32824e2c515f0e0f2d6ecf2f1 |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < fdcb263fa5cda15b8cb24a641fa2718c47605314 | fdcb263fa5cda15b8cb24a641fa2718c47605314 |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < 8b1087b998e273f07be13dcb5f3ca4c309c7f108 | 8b1087b998e273f07be13dcb5f3ca4c309c7f108 |
| linux | linux | >= fc4099f17240767554ff3a73977acb78ef615404 < 9eeabdf17fa0ab75381045c867c370f4cc75a613 | 9eeabdf17fa0ab75381045c867c370f4cc75a613 |
| linux | linux_kernel | >= 0 < 5.10.103-1 | 5.10.103-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 4.10 < 4.14.267 | 4.14.267 |
| linux | linux_kernel | >= 4.15 < 4.19.230 | 4.19.230 |
| linux | linux_kernel | >= 4.20 < 5.4.180 | 5.4.180 |
| linux | linux_kernel | >= 4.3 < 4.9.302 | 4.9.302 |
| linux | linux_kernel | >= 5.11 < 5.15.24 | 5.15.24 |
| linux | linux_kernel | >= 5.16 < 5.16.10 | 5.16.10 |
| linux | linux_kernel | >= 5.5 < 5.10.101 | 5.10.101 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-48809: 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 sk
osv·2024-07-16·CVSS 5.5
CVE-2022-48809 [MEDIUM] CVE-2022-48809: 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 sk
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.
GHSA
GHSA-7jv7-gr8j-4554: 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
ghsa_unreviewed·2024-07-16
CVE-2022-48809 [MEDIUM] CWE-401 GHSA-7jv7-gr8j-4554: 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
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.
Red Hat
kernel: net: fix a memleak when uncloning an skb dst and its metadata
vendor_redhat·2024-07-16·CVSS 5.5
CVE-2022-48809 [MEDIUM] CWE-402 kernel: net: fix a memleak when uncloning an skb dst and its metadata
kernel: net: fix a memleak when uncloning an skb dst and its metadata
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_d
Debian
CVE-2022-48809: linux - In the Linux kernel, the following vulnerability has been resolved: net: fix a ...
vendor_debian·2022·CVSS 5.5
CVE-2022-48809 [MEDIUM] CVE-2022-48809: linux - In the Linux kernel, the following vulnerability has been resolved: net: fix a ...
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.
Scope: local
boo
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/00e6d6c3bc14dfe32824e2c515f0e0f2d6ecf2f1https://git.kernel.org/stable/c/0be943916d781df2b652793bb2d3ae4f9624c10ahttps://git.kernel.org/stable/c/4ac84498fbe84a00e7aef185e2bb3e40ce71eca4https://git.kernel.org/stable/c/8b1087b998e273f07be13dcb5f3ca4c309c7f108https://git.kernel.org/stable/c/9eeabdf17fa0ab75381045c867c370f4cc75a613https://git.kernel.org/stable/c/a80817adc2a4c1ba26a7aa5f3ed886e4a18dff88https://git.kernel.org/stable/c/c1ff27d100e2670b03cbfddb9117e5f9fc672540https://git.kernel.org/stable/c/fdcb263fa5cda15b8cb24a641fa2718c47605314https://git.kernel.org/stable/c/00e6d6c3bc14dfe32824e2c515f0e0f2d6ecf2f1https://git.kernel.org/stable/c/0be943916d781df2b652793bb2d3ae4f9624c10ahttps://git.kernel.org/stable/c/4ac84498fbe84a00e7aef185e2bb3e40ce71eca4https://git.kernel.org/stable/c/8b1087b998e273f07be13dcb5f3ca4c309c7f108https://git.kernel.org/stable/c/9eeabdf17fa0ab75381045c867c370f4cc75a613https://git.kernel.org/stable/c/a80817adc2a4c1ba26a7aa5f3ed886e4a18dff88https://git.kernel.org/stable/c/c1ff27d100e2670b03cbfddb9117e5f9fc672540https://git.kernel.org/stable/c/fdcb263fa5cda15b8cb24a641fa2718c47605314
2024-07-16
Published