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

> A missing NULL check in the TPS6594 regulator driver can cause a kernel crash via null pointer dereference during device probing.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93273, DEBIAN-CVE-2026-93273, GHSA-f775-wj9m-j2c6, UBUNTU-CVE-2026-93273

## What is CVE-2026-93273?

CVE-2026-93273 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-93273?


## How do I fix CVE-2026-93273?

Apply the vendor's patch.

## Is CVE-2026-93273 being exploited?

There is no known exploitation of CVE-2026-93273 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93273 and fix it if it is affected.

What it is: CVE-2026-93273 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93273 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93273/ (Markdown: https://insights.sbomify.com/CVE-2026-93273/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93273
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93273
- OSV: https://osv.dev/vulnerability/CVE-2026-93273

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93273/
Summaries are generated and may contain mistakes; the official description above is the record.