From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93145][LOW] clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister() [ Upstream Date: Thu, 17 Sep 2026 21:05:42 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93145 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: 2 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: 418d2f0a32b2a9ceb656a88aa9139408a9b7b517 List-Id: CVE: CVE-2026-93145 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister() [ Upstream Commit: 418d2f0a32b2a9ceb656a88aa9139408a9b7b517 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=418d2f0a32b2a9ceb656a88aa9139408a9b7b517 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93145 Analysis date: Thu, 17 Sep 2026 21:05:42 -0400 ActionableScore: 2 ActionableScore lower bound: 1 Actionable bucket: Ordinary Moderate Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93145 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93145 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: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-93145 LOW https://www.kernelcve.org/list/?q=CVE-2026-93145 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:L/UI:N/S:U/C:L/I:L/A:H';*CWE-772;*CWE-664;CWE-362;*CWE-416;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.8';DESCR 'gdsc_unregister did not remove per-domain generic PM domain objects from the global genpd list during provider teardown. This can leave stale gpd_list entries after an unbind/rebind cycle, deferred probe replay, module unload, or OF overlay removal, causing later gdsc_init registration to fail with EEXIST and potentially preventing device recovery. A racing consumer lookup may also attach to a domain that is already in mid-removal if the OF provider remains visible during teardown. For the CVSS the PR:L value is used in the paranoid score because some systems may delegate device or overlay management to a reduced capability root, service account, or constrained management domain rather than a full host administrator. The issue is not network reachable. Impact is at least local denial of service and in the worst still defensible interpretation may include limited confidentiality or integrity impact if stale genpd entries become a use-after-free candidate during later list traversal.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) YES HARDWARE LINUS NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=1 PrimitiveClass=CLASS_B RealUAF=NO HostAdminRequired=YES NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1. No floor or cap changed the score. * Raw paranoid score: 2 * Paranoid score: 2. No floor or cap changed the score. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown Conservative signals: * +1 Concrete persistent kernel resource/reference leak. `gdsc_unregister()` removes the OF provider but does not call `pm_genpd_remove()` for each registered `generic_pm_domain`, leaving entries in the global `gpd_list`. * +1 Active-state retirement bypass. The normal genpd retirement operation exists and is restored by the patch, and the stale registration remains active enough to affect later `pm_genpd_init()` behavior. * +1 Availability impact. A later provider rebind can fail with `-EEXIST`, preventing successful device/domain recovery. * -2 Host-admin-equivalent trigger. The described trigger paths are provider unbind/rebind, module unload, OF-overlay teardown, or early boot deferred-probe replay, which are host device-management operations. Paranoid additional signal: * +1 Weak indirect lifetime/consistency concern. The commit explicitly notes that a racing `of_genpd_get_from_provider()` could attach to a domain while it is in mid-removal. This supports manual review, but does not establish controlled corruption. Important non-awarded signals: * Real UAF not awarded. The patch establishes stale global genpd registration entries, but does not directly show dereference of freed heap/module memory. * Controlled reclaim not demonstrated. * Arbitrary read/write not demonstrated. * Concrete repeated release/refcount mutation not established. * Structured stale-object exploitation leverage not awarded because no attacker-controlled replacement or meaningful post-free field consumption is shown. * C/I impact not awarded. The evidence supports stale registration and availability failure, not disclosure or unauthorized modification. * Remote reachability not established. * Race penalty not applied. The race is noted, but the main demonstrated failure is stale registration after teardown, not a hard attacker-controlled timing race. 3. Reachability analysis The reachable scenarios are provider unbind/rebind, real module unload of a clock driver owning GDSCs, OF-overlay teardown, or deferred-probe replay during early boot. These are not ordinary local-user operations. They normally require host root or host-admin-equivalent device-management authority. The complete trigger chain is not namespace-scoped. GDSC, genpd, OF provider registration, module unload, and OF overlay teardown are global kernel/device-management operations, not attacker-created user or network namespace operations. No network trigger is established. No special external packet or remote input path reaches the vulnerable operation. No special rare hardware penalty is applied beyond the host-admin device-management requirement, because the code is hardware/platform specific but the scoring already accounts for the privileged management path. 4. Primitive and severity interpretation The exact primitive is a missing teardown of per-domain genpd registrations. This leaves stale active entries in the global genpd list and can cause later re-registration failure. It is best treated as a CLASS_B active-state lifetime/registration consistency violation, not as a proven memory UAF. The demonstrated consequence is local availability impact: failed rebind or recovery due to `-EEXIST`. The racing provider lookup concern suggests a possible unsafe mid-removal attachment, but the patch does not establish controlled reclaim, arbitrary write, callback control, disclosure, or privilege escalation. ImportantCandidate is NO because the evidence does not show a strong corruption primitive, security-boundary bypass, repeated lifetime/refcount mutation, or below-host-admin reachability. ManualReview is RECOMMENDED because stale global lifecycle state and the mid-removal consumer race deserve source review. AutoDowngradeAllowed is YES because the established impact is constrained and host-admin gated. Likely operational severity: Low to ordinary Moderate. 5. One-sentence report phrase A missing `pm_genpd_remove()` in `gdsc_unregister()` leaves stale genpd registrations after provider teardown, which can break later rebind or recovery and may allow a racing consumer lookup to attach to a domain during removal. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Reason: stale global genpd lifecycle state is established, but the supplied evidence mainly supports availability/recovery failure rather than a proven memory-corruption or privilege-escalation primitive. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister() [ Upstream Commit: 418d2f0a32b2a9ceb656a88aa9139408a9b7b517 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=418d2f0a32b2a9ceb656a88aa9139408a9b7b517 Changed files: drivers/clk/qcom/gdsc.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=418d2f0a32b2a9ceb656a88aa9139408a9b7b517 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93145 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93145 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: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H The Best / paranoid CVSS score: 5.8 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: 1 Paranoid ActionableScore: 2 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).