CVE-2026-64301: regulator: scmi: fix of_node refcount leak in scmi_regulator_probe()
Noroxi assessment
Priority: Monitor (action score 22/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1e446e8f8c763be3de7d0362e024cdf46194ffef, 22cb337370e6539b0418832c6040e9b00c1b74ca, 3e1441a4d06d35a314961e40057bd1f0106bbc14.
Low priority for now. Upgrade to Linux Linux 1e446e8f8c763be3de7d0362e024cdf46194ffef, 22cb337370e6539b0418832c6040e9b00c1b74ca, 3e1441a4d06d35a314961e40057bd1f0106bbc14 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: scmi: fix of_node refcount leak in scmi_regulator_probe() scmi_regulator_probe() calls of_find_node_by_name() which takes a reference on the returned device node. On the error path where process_scmi_regulator_of_node() fails, the function returns without calling of_node_put() on the child node, leaking the reference. Add of_node_put(np) on the error path to properly release the reference.
- Published
- Jul 25, 2026
- Updated
- Sep 3, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.11 and later · before 5.15.212
- linux linux kernel5.16 and later · before 6.1.178
- linux linux kernel6.2 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.96
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
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
- 5.11affected
- 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and later · before 1e446e8f8c763be3de7d0362e024cdf46194ffefaffected · git
- 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and later · before 637c11e3d8d43a7ee654591cda8d17c55a9234faaffected · git
- 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and later · before e2baf8ea13fb4b10bec2c4751aea05c00dabcd0faffected · git
- 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and later · before 3e1441a4d06d35a314961e40057bd1f0106bbc14affected · git
- 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and later · before 22cb337370e6539b0418832c6040e9b00c1b74caaffected · git
- 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and later · before a935b64548fcfe1d5b4dbdd31dddfb0d7019367faffected · git
- 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and later · before fa11039d6cdff84584a3ef8cc1f5e1b56e045da2affected · git
- before 5.11not affected · semver
- 5.15.212 and later · up to and including 5.15.*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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64297Jul 25, 2026 · module: decompress: check return value of module_extend_max_pages()22Monitor
- ← EarlierCVE-2026-64300Jul 25, 2026 · perf/aux: Fix page UAF in map_range()31Monitor
- Later →CVE-2026-64302Jul 25, 2026 · x86/mm: Fix freeing of PMD-sized vmemmap pages22Monitor
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 | 1e446e8f8c763be3de7d0362e024cdf46194ffef | Vendor (CNA) |
| Linux Linux | 22cb337370e6539b0418832c6040e9b00c1b74ca | Vendor (CNA) |
| Linux Linux | 3e1441a4d06d35a314961e40057bd1f0106bbc14 | Vendor (CNA) |
| Linux Linux | 637c11e3d8d43a7ee654591cda8d17c55a9234fa | Vendor (CNA) |
| Linux Linux | a935b64548fcfe1d5b4dbdd31dddfb0d7019367f | Vendor (CNA) |
| Linux Linux | e2baf8ea13fb4b10bec2c4751aea05c00dabcd0f | Vendor (CNA) |
| Linux Linux | fa11039d6cdff84584a3ef8cc1f5e1b56e045da2 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (6 more)Show less
- git.kernel.org/stable/c/22cb337370e6539b0418832c6040e9b00c1b74ca
- git.kernel.org/stable/c/3e1441a4d06d35a314961e40057bd1f0106bbc14
- git.kernel.org/stable/c/637c11e3d8d43a7ee654591cda8d17c55a9234fa
- git.kernel.org/stable/c/a935b64548fcfe1d5b4dbdd31dddfb0d7019367f
- git.kernel.org/stable/c/e2baf8ea13fb4b10bec2c4751aea05c00dabcd0f
- git.kernel.org/stable/c/fa11039d6cdff84584a3ef8cc1f5e1b56e045da2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.