CVE Catalog

CVE-2026-93273

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the tps6594_regulator_probe() multiphase configuration loop failed to release device node references (np, np_parent, np_pmic_parent) obtained via of_find_node_by_name() and of_get_parent(), causing a reference leak on every iteration. Additionally, a missing NULL check after of_find_node_by_name() could lead to a NULL pointer dereference.

Risk Assessment

The device tree node reference leak can gradually exhaust kernel resources and, in extreme cases, cause a system crash (NULL pointer dereference) during TPS6594 regulator initialization.

Recommendation

Update the Linux kernel to a version containing the fix that adds a NULL check and of_node_put() calls for np, np_parent, and np_pmic_parent on each loop iteration.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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

Vulnerability data from NVD (NIST) · CISA KEV · EPSS