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-50246usb: typec: tcpci: fix of node refcount leak in tcpci_register_port()

Description

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in tcpci_unregister_port() to avoid leak.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 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-50246, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.17% · top 94% of all CVEs (15 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 5e85a04c8c0d271d7561a770b85741f186398868 – < 4f257e2eba419ab4cd880c822346450e4e7b2af3
    • affected 5e85a04c8c0d271d7561a770b85741f186398868 – < d3b6c28a71f111a6c67ddc3238aab95910fd86cf
    • affected 5e85a04c8c0d271d7561a770b85741f186398868 – < ba75be6f0d9d028d20852564206565a4c03e3288
    • affected 5e85a04c8c0d271d7561a770b85741f186398868 – < e75a324409715bd71348f79a49aa61b69dbeb676
    • affected 5e85a04c8c0d271d7561a770b85741f186398868 – < 5f125507d2270035dfcf83fbff6cff5a143e200c
    • affected 5e85a04c8c0d271d7561a770b85741f186398868 – < 0384e87e3fec735e47f1c133c796f32ef7a72a9b
  • Linux · Linux

    • affected 4.19
    • unaffected < 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

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .