CVE-2026-93273: regulator: tps6594: Fix device node reference leaks in multiphase loop
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 28f70e0aa767a8f022c70ed75ecef227dc668121, 4a672bff99f6b58dde419fd12b3a53da137f032d, 68ce4f8223b78f8616ec7f4a02c38988eae627d2; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 28f70e0aa767a8f022c70ed75ecef227dc668121, 4a672bff99f6b58dde419fd12b3a53da137f032d, 68ce4f8223b78f8616ec7f4a02c38988eae627d2; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Sep 24, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.5affected
- f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 and later · before 28f70e0aa767a8f022c70ed75ecef227dc668121affected · git
- f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 and later · before 4a672bff99f6b58dde419fd12b3a53da137f032daffected · git
- f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 and later · before 68ce4f8223b78f8616ec7f4a02c38988eae627d2affected · git
- f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 and later · before fceac25487b21d6db940d2aed368e465d89cd1f4affected · git
- f17ccc5deb4d024bb52fd3433471e77ab7ae9ad8 and later · before 7fd28093b3effc4f92566466df364622830ec608affected · git
- before 6.5not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
- 6.12.110 and later · up to and including 6.12.*not affected · semver
- 6.18.52 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93271Sep 24, 2026 · wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate0Monitor
- ← EarlierCVE-2026-93272Sep 24, 2026 · remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v30Monitor
- Later →CVE-2026-93274Sep 24, 2026 · pinctrl: bcm2835: Don't remove an unregistered GPIO chip0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 28f70e0aa767a8f022c70ed75ecef227dc668121 | Vendor (CNA) |
| Linux Linux | 4a672bff99f6b58dde419fd12b3a53da137f032d | Vendor (CNA) |
| Linux Linux | 68ce4f8223b78f8616ec7f4a02c38988eae627d2 | Vendor (CNA) |
| Linux Linux | 7fd28093b3effc4f92566466df364622830ec608 | Vendor (CNA) |
| Linux Linux | fceac25487b21d6db940d2aed368e465d89cd1f4 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.