Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50349misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()

Description

In the Linux kernel, the following vulnerability has been resolved: misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() If device_register() returns error in tifm_7xx1_switch_media(), name of kobject which is allocated in dev_set_name() called in device_add() is leaked. Never directly free @dev after calling device_register(), even if it returned an error! Always use put_device() to give up the reference initialized.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50349, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.16% · top 94% of all CVEs (13 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.

Affected products

  • Linux · Linux

    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < 2bbb222a54ff501f77ce593d21b76b79c905045e
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < d861b7d41b17942b337d4b87a70de7cd1dc44d4e
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < 1695b1adcc3a7d985cd22fa3b55761edf3fab50d
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < ee2715faf7e7153f5142ed09aacfa89a64d45dcb
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < 57c857353d5020bdec8284d9c0fee447484fe5e0
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < 848c45964ded537107e010aaf353aa30a0855387
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < 35abbc8406cc39e72d3ce85f6e869555afe50d54
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < ef843ee20576039126d34d6eb5f45d14c3e6ce18
    • affected 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79 – < fd2c930cf6a5b9176382c15f9acb1996e76e25ad
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .