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-2026-93273regulator: tps6594: Fix device node reference leaks in multiphase loop

Description

In the Linux kernel, the following vulnerability has been resolved: regulator: tps6594: Fix device node reference leaks in multiphase loop In tps6594_regulator_probe(), the multi-phase configuration loop calls of_find_node_by_name() to find buck nodes by name, and of_get_parent() twice to navigate to the PMIC parent node. None of the acquired node references (np, intermediate parent, np_pmic_parent) are ever released via of_node_put(), causing a reference leak on every loop iteration. Additionally, of_find_node_by_name() can return NULL, but the result was immediately passed to of_node_full_name() and of_get_parent() without a NULL check, which could lead to a NULL pointer dereference. Fix this by: - Adding a NULL check for np after of_find_node_by_name() - Storing the intermediate parent node in a local variable np_parent - Calling of_node_put() on np, np_parent and np_pmic_parent at the end of each loop iteration

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days 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: Received.

EPSS (exploitation in 30 days)
0.19% · top 92% of all CVEs (16 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 f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 – < 28f70e0aa767a8f022c70ed75ecef227dc668121
    • affected f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 – < 4a672bff99f6b58dde419fd12b3a53da137f032d
    • affected f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 – < 68ce4f8223b78f8616ec7f4a02c38988eae627d2
    • affected f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 – < fceac25487b21d6db940d2aed368e465d89cd1f4
    • affected f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 – < 7fd28093b3effc4f92566466df364622830ec608
  • Linux · Linux

    • affected 6.5
    • unaffected < 6.5
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .