From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-64301][LOW] regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() [ Upstream Date: Sat, 25 Jul 2026 06:59:44 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-64301 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 1e446e8f8c763be3de7d0362e024cdf46194ffef List-Id: CVE: CVE-2026-64301 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() [ Upstream Commit: 1e446e8f8c763be3de7d0362e024cdf46194ffef Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1e446e8f8c763be3de7d0362e024cdf46194ffef Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64301 Analysis date: Sat, 25 Jul 2026 06:59:44 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: YES Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-64301 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64301 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: LOW Manual review required: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-64301 LOW CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';*CWE-772;*CWE-401;CWE-404;BEST CVSS score: '1.9';DESCR 'scmi_regulator_probe can leak a reference to a device tree node when process_scmi_regulator_of_node fails with ENOMEM. The leaked reference comes from of_find_node_by_name and is not released on this error path, which can leave the node reference count elevated after probe failure. For the CVSS the PR:H is used because reliable triggering normally requires control over driver probe or platform device management and also requires hitting the ENOMEM error path. The issue is not network reachable and does not provide a clear memory corruption primitive. Impact is limited to a low availability risk from a small reference leak rather than privilege escalation or information disclosure.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0) YES NOMEMCHK SIMPLEFIX LEAK ERRORPATH HARDWARE YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 1. ActionableScore * Conservative score: 0 * Paranoid score: 0 * Final recommended bucket: **Ordinary Moderate / Low-like** 2. Signal breakdown * Availability impact realistic: +0. The bug is a small device-node reference leak on an ENOMEM error path, but the patch does not show a reliable system-wide DoS condition. * Requires admin/root/device-management control in typical deployments: -2. Reliable triggering normally requires influencing SCMI regulator probe or platform device setup, plus forcing the specific ENOMEM failure path. * Rare and difficult-to-reach subsystem/configuration: -1. SCMI regulator probing is platform/firmware dependent and not a common unprivileged attack surface. * No memory corruption signal. This is a missing of_node_put() reference release, not UAF, double-free, OOB access, arbitrary write, type confusion, or stale callback use. * No LPE signal. There is no reclaim, overwrite, object replacement, or security-boundary bypass primitive. 3. Reachability analysis The bug is reachable only during scmi_regulator_probe() and only when process_scmi_regulator_of_node() returns -ENOMEM inside the child-node loop. A normal local unprivileged user cannot directly trigger this path in typical deployments. Namespaces or containers do not meaningfully lower the privilege requirement because SCMI regulator probing and device-tree backed platform setup are host-controlled. The path is not network reachable. Realistic exploitation conditions are weak because the attacker would need both probe influence and a controlled memory allocation failure. 4. Severity interpretation This behaves like a Low or ordinary Moderate cleanup/resource-leak issue, not an actionable Moderate or Important kernel vulnerability. Theoretical impact is limited availability degradation from a leaked device-node reference if the failing probe path can be repeated. Realistic exploitation evidence does not support memory corruption, privilege escalation, confidentiality impact, integrity impact, or a reliable kernel crash. 5. One-sentence report phrase A missing of_node_put() in the SCMI regulator probe ENOMEM error path leaks a device tree node reference, but it requires privileged device-management conditions and has only low availability impact. 6. Manual review recommendation NO MANUAL CHECK NEEDED. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED. Reason: reference leak only, no memory corruption primitive, no network reachability, no unprivileged trigger, and no plausible privilege-escalation path from the patch context. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: regulator: scmi: fix of_node refcount leak in scmi_regulator_probe() [ Upstream Commit: 1e446e8f8c763be3de7d0362e024cdf46194ffef Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1e446e8f8c763be3de7d0362e024cdf46194ffef Changed files: drivers/regulator/scmi-regulator.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1e446e8f8c763be3de7d0362e024cdf46194ffef ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-64301 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64301 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: Not available The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS score: 1.9 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 0 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).