Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48809

net: fix a memleak when uncloning an skb dst and its metadata

Medium5.5EPSS 0.28%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2022-48809, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected fc4099f17240767554ff3a73977acb78ef615404 – < 4ac84498fbe84a00e7aef185e2bb3e40ce71eca4
    • affected fc4099f17240767554ff3a73977acb78ef615404 – < c1ff27d100e2670b03cbfddb9117e5f9fc672540
    • affected fc4099f17240767554ff3a73977acb78ef615404 – < 0be943916d781df2b652793bb2d3ae4f9624c10a
    • affected fc4099f17240767554ff3a73977acb78ef615404 – < a80817adc2a4c1ba26a7aa5f3ed886e4a18dff88
    • affected fc4099f17240767554ff3a73977acb78ef615404 – < 00e6d6c3bc14dfe32824e2c515f0e0f2d6ecf2f1
    • affected fc4099f17240767554ff3a73977acb78ef615404 – < fdcb263fa5cda15b8cb24a641fa2718c47605314
    • affected fc4099f17240767554ff3a73977acb78ef615404 – < 8b1087b998e273f07be13dcb5f3ca4c309c7f108
    • affected fc4099f17240767554ff3a73977acb78ef615404 – < 9eeabdf17fa0ab75381045c867c370f4cc75a613
  • Linux · Linux

    • affected 4.3
    • unaffected < 4.3
    • unaffected 4.9.302 – ≤ 4.9.*
    • unaffected 4.14.267 – ≤ 4.14.*
    • unaffected 4.19.230 – ≤ 4.19.*
    • unaffected 5.4.180 – ≤ 5.4.*
    • unaffected 5.10.101 – ≤ 5.10.*
    • unaffected 5.15.24 – ≤ 5.15.*
    • unaffected 5.16.10 – ≤ 5.16.*
    • unaffected 5.17 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48809 badge
[![CVE-2022-48809](https://trackcve.app/badge/CVE-2022-48809.svg)](https://trackcve.app/cve/CVE-2022-48809)

Record last updated .