Resource leak via unreleased device-node reference
Published Jul 25, 2026 · Updated Jul 25, 2026
Resource leak in the Linux Kernel SCMI regulator driver allows attackers to retain a device-node reference via unspecified vectors. On the process_scmi_regulator_of_node() error path, scmi_regulator_probe() returns after of_find_node_by_name() without calling of_node_put() on the child node. The public record identifies neither an attacker-controlled trigger nor a resulting crash, hang, or other service impact.
Summary
What happened
Resource leak in the Linux Kernel SCMI regulator driver allows attackers to retain a device-node reference via unspecified vectors. On the process_scmi_regulator_of_node() error path, scmi_regulator_probe() returns after of_find_node_by_name() without calling of_node_put() on the child node. The public record identifies neither an attacker-controlled trigger nor a resulting crash, hang, or other service impact.
The record
- CVE
- CVE-2026-64301
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0fbeae70ee7ce98e18a47337cd1f205dd88589e9 <1e446e8f8c763be3de7d0362e024cdf46194ffef
- Affected versionversion=0fbeae70ee7ce98e18a47337cd1f205dd88589e9 <22cb337370e6539b0418832c6040e9b00c1b74ca
- Affected versionversion=0fbeae70ee7ce98e18a47337cd1f205dd88589e9 <3e1441a4d06d35a314961e40057bd1f0106bbc14
- Affected versionversion=0fbeae70ee7ce98e18a47337cd1f205dd88589e9 <637c11e3d8d43a7ee654591cda8d17c55a9234fa
- Affected versionversion=0fbeae70ee7ce98e18a47337cd1f205dd88589e9 <a935b64548fcfe1d5b4dbdd31dddfb0d7019367f
- Affected versionversion=0fbeae70ee7ce98e18a47337cd1f205dd88589e9 <e2baf8ea13fb4b10bec2c4751aea05c00dabcd0f
- Affected versionversion=0fbeae70ee7ce98e18a47337cd1f205dd88589e9 <fa11039d6cdff84584a3ef8cc1f5e1b56e045da2
- Affected versionversion=5.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo