CVE-2022-48809
Last modified
CVE-2022-48809 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.28% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.3, < 4.9.302 |
| Linux | Linux Kernel | >= 4.10, < 4.14.267 |
| Linux | Linux Kernel | >= 4.15, < 4.19.230 |
| Linux | Linux Kernel | >= 4.20, < 5.4.180 |
| Linux | Linux Kernel | >= 5.5, < 5.10.101 |
| Linux | Linux Kernel | >= 5.11, < 5.15.24 |
| Linux | Linux Kernel | >= 5.16, < 5.16.10 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-48809?
How severe is CVE-2022-48809?
How do I fix CVE-2022-48809?
Are you affected by CVE-2022-48809?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
