From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93116][LOW] platform/x86: asus-wmi: fix resource leaks on probe failure [ Upstream Date: Fri, 18 Sep 2026 08:35:04 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93116 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: 3308b8c5f5a28403611a2f5a46f06aabe4f0c661 List-Id: CVE: CVE-2026-93116 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: platform/x86: asus-wmi: fix resource leaks on probe failure [ Upstream Commit: 3308b8c5f5a28403611a2f5a46f06aabe4f0c661 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3308b8c5f5a28403611a2f5a46f06aabe4f0c661 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93116 Analysis date: Fri, 18 Sep 2026 08:35:04 -0400 ActionableScore: 0 ActionableScore lower bound: unknown 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-93116 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93116 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-93116 LOW https://www.kernelcve.org/list/?q=CVE-2026-93116 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:H';*CWE-772;CWE-404;*CWE-401;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'The asus-wmi probe failure path can leak resources because some error labels are not ordered in the reverse order of successful registrations. A failure in custom fan curve initialization can bypass cleanup for input and sysfs resources, and a failure in screenpad initialization can bypass cleanup for backlight and rfkill resources. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over driver load, bind, unbind, or reprobe operations on a matching ASUS WMI platform. The issue is not network reachable and does not provide a direct memory corruption primitive. Impact is limited to local denial of service through resource leakage, mainly if failed probe attempts can be repeated.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) SKIP CVE-2026-93116 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE INIT SIMPLEFIX LEAK ERRORPATH HARDWARE - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=YES NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: -1 * Conservative score: 0 * Raw paranoid score: -1 * Paranoid score: 0 * Applied conservative floor/cap: lower bound applied, -1 -> 0 * Applied paranoid floor/cap: lower bound applied, -1 -> 0 * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown Positive signals: * +1 Concrete persistent kernel resource/reference leak. The patch directly establishes that already registered sysfs, input, backlight, and rfkill resources can be skipped during probe-failure cleanup because error labels were ordered incorrectly. Negative signals: * -2 Host-admin-equivalent triggering requirement. Reliable triggering requires control over driver load, bind, unbind, reprobe, or equivalent platform-driver management on a matching ASUS WMI system. Non-awarded material signals: * RealUAF not awarded. The patch shows skipped cleanup and leaked resources, not use-after-free or stale post-lifetime object use. * Concrete repeated release/refcount not awarded. There is no first release followed by a second lifetime-mutating operation on the same dangling reference. * Reliable kernel crash not awarded. The described impact is resource leakage, not a demonstrated Oops, panic, or host-wide fatal fault. * Extra resource-exhaustion point not awarded. Repeated failures could accumulate leaks, but this remains host-admin-gated and no broad isolation bypass or ordinary-user host-wide exhaustion is established. * C/I impact not awarded. No disclosure, unauthorized write, memory corruption, security-boundary bypass, or privilege-escalation primitive is shown. * Remote reachability not established. * Controlled reclaim, arbitrary write, object replacement, callback influence, and LPE are not demonstrated. 3. Reachability analysis The vulnerable path is the asus-wmi platform driver probe failure path. A practical attacker would need to cause selected initialization failures and repeat driver probing or binding on a matching ASUS WMI platform. That normally requires host-admin-equivalent control over module or platform-driver lifecycle operations. This is not namespace-scoped. No user namespace or network namespace capability path is involved. There is no network trigger. Prior hardware or firmware context is relevant only because the driver applies to ASUS WMI platforms, but the key reducing factor is host-admin control of probe/reprobe rather than rare hardware. No race or timing primitive is involved. 4. Primitive and severity interpretation The exact primitive is a resource cleanup omission on an error path. It is not an active structured UAF, not fixed stale storage, and not a repeated release/refcount mutation. The demonstrated consequence is leaked kernel driver resources after failed probe attempts. Speculative consequence is local denial of service through repeated resource leakage, but only under host-admin-equivalent control. There is no meaningful leverage beyond resource consumption. PrimitiveClass is NONE because no corruption, ownership violation, authorization bypass, or lifetime mutation through a dangling object is established. ImportantCandidate=NO because the issue is a host-admin-gated resource leak without memory corruption or a security-boundary primitive. AutoDowngradeAllowed=YES because automatic low-priority handling would not discard an unresolved Important-grade primitive. Likely operational severity is low to ordinary Moderate. 5. One-sentence report phrase The asus-wmi probe failure path can leak registered driver resources due to incorrectly ordered cleanup labels, but reliable triggering requires host administrative driver lifecycle control and the demonstrated impact is limited to local resource-leak DoS. 6. Manual review recommendation NO MANUAL CHECK NEEDED Reason: this is a host-admin-gated resource leak with no UAF, no repeated refcount mutation, no memory corruption, no network reachability, and no authorization-boundary bypass. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: platform/x86: asus-wmi: fix resource leaks on probe failure [ Upstream Commit: 3308b8c5f5a28403611a2f5a46f06aabe4f0c661 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3308b8c5f5a28403611a2f5a46f06aabe4f0c661 Changed files: drivers/platform/x86/asus-wmi.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=3308b8c5f5a28403611a2f5a46f06aabe4f0c661 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93116 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93116 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:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.1 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).