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-50887regulator: core: fix unbalanced of node refcount in regulator_dev_lookup()

Description

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix unbalanced of node refcount in regulator_dev_lookup() I got the the following report: 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@62/regulators/exten In of_get_regulator(), the node is returned from of_parse_phandle() with refcount incremented, after using it, of_node_put() need be called.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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.24% · top 85% 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 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < 0e88505ac0a6ae97746bcdbd4b042ee9f20455ae
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < 4dfcf5087db9a34a300d6b99009232d4537c3e6a
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < 3ac888db0f67813d91373a9a61c840f815cd4ec9
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < d39937f8de641c44a337cec4a2e5d3e8add20a7d
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < f48c474efe05cf9ce5e535b5e0ddd710e963936c
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < cda1895f3b7f324ece1614308a815a3994983b97
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < 2b93c58adddd98812ad928bbc2063038f3df1ffd
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < 2f98469c3141f8e42ba11075a273fb795bbad57f
    • affected 69511a452e6dc6b74fe4f3671a51b1b44b9c57e3 – < f2b41b748c19962b82709d9f23c6b2b0ce9d2f91
  • Linux · Linux

    • affected 3.3
    • unaffected < 3.3
    • 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-50887 badge
[![CVE-2022-50887](https://cveledger.app/badge/CVE-2022-50887.svg)](https://cveledger.app/cve/CVE-2022-50887)

Record last updated .