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-50703soc: qcom: smsm: Fix refcount leak bugs in qcom_smsm_probe()

Description

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: smsm: Fix refcount leak bugs in qcom_smsm_probe() There are two refcount leak bugs in qcom_smsm_probe(): (1) The 'local_node' is escaped out from for_each_child_of_node() as the break of iteration, we should call of_node_put() for it in error path or when it is not used anymore. (2) The 'node' is escaped out from for_each_available_child_of_node() as the 'goto', we should call of_node_put() for it in goto target.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c97c4090ff72297a878a37715bd301624b71c885 – < 1bbe75d466e5118b7d49ef4a346c3ce5742da4e8
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < bd4666bf5562fe8e8e5e9bd6fc805d30e1767f43
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < 42df28994eba7b56c762f7bbe7efd5611a1cd15b
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < 1e3ed59370c712df436791efed120f0c082aa9bc
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < 39781c98ad46b4e85053345dff797240c1ed7935
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < 96e0028debdd07a6d582f0dfadf9a3ec2b5fffff
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < 8fb6112bd49c0e49f2cf51604231d85ff00284bb
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < ee7fc83ce0e6986ff9b1c1d7e994fbbf8d43861d
    • affected c97c4090ff72297a878a37715bd301624b71c885 – < af8f6f39b8afd772fda4f8e61823ef8c021bf382
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 4.9.331 – ≤ 4.9.*
    • unaffected 4.14.296 – ≤ 4.14.*
    • unaffected 4.19.262 – ≤ 4.19.*
    • unaffected 5.4.220 – ≤ 5.4.*
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .