From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93126][LOW] remoteproc: qcom_q6v5_adsp: Fix reference leak for device node [ Upstream Date: Thu, 17 Sep 2026 15:07:17 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93126 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: a73cfa80f1ec6b0f948cf3c91455c62423747b3e List-Id: CVE: CVE-2026-93126 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: remoteproc: qcom_q6v5_adsp: Fix reference leak for device node [ Upstream Commit: a73cfa80f1ec6b0f948cf3c91455c62423747b3e Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a73cfa80f1ec6b0f948cf3c91455c62423747b3e Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93126 Analysis date: Thu, 17 Sep 2026 15:07:17 -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-93126 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93126 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-93126 LOW https://www.kernelcve.org/list/?q=CVE-2026-93126 CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-772;*CWE-401;CWE-404;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'A reference leak in qcom_q6v5_adsp occurs because adsp_map_carveout calls of_parse_phandle_with_args and does not release the returned device node reference. This can leak OF node references during ADSP remoteproc setup or repeated device lifecycle operations and may eventually contribute to resource exhaustion on affected Qualcomm platforms. For the CVSS the PR:H is selected because reliable triggering normally requires administrative control over remoteproc start, driver reprobe, or device management on the host. The issue is not network reachable and is not triggered by packet traffic. Impact is limited to denial of service through resource leakage. There is no evidence of a UAF, OOB access, information disclosure, or privilege escalation primitive in this patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) YES SIMPLEFIX LEAK HARDWARE LINUS YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=1 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=YES NamespaceScopedPrivilege=NO ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 2 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate**:: No floor or cap changed the score. The paranoid score is higher only because repeated remoteproc lifecycle operations could make the reference leak accumulate, but there is still no kernel corruption, UAF, authorization bypass, or privilege escalation primitive. 2. Signal breakdown Positive signals: * +1 Concrete persistent kernel resource/reference leak. `of_parse_phandle_with_args()` returns a referenced device node in `args.np`, and the old code failed to release it with `of_node_put()`. * +1 Paranoid only: possible accumulated resource pressure if an administrator can repeatedly drive ADSP remoteproc setup, teardown, reprobe, or related lifecycle operations. Negative or non-awarded signals: * Host-admin/device-management reachability is supported by the remoteproc ADSP setup context. This keeps the issue in the ordinary bucket. * RealUAF not awarded. The patch fixes a missing put, not a stale post-free use. * Concrete repeated release/refcount not awarded. There is no first put that may free the object followed by a second put on the same dangling reference. * Reliable kernel crash not awarded. The supplied evidence shows a reference leak, not an immediate Oops, panic, or fatal dereference. * Confidentiality and integrity not awarded. No disclosure path, unauthorized write, ownership violation, or security-boundary bypass is established. * Strong or weak LPE leverage not awarded. There is no controlled reclaim, arbitrary write, callback influence, refcount takeover, or active stale-object use. * Remote reachability not awarded. This is not triggered by packet traffic or an externally reachable protocol path. * Extra availability beyond resource leakage not awarded. Sustained exhaustion is only a paranoid operational concern. 3. Reachability analysis The vulnerable path is in Qualcomm ADSP remoteproc carveout setup. Practical triggering appears tied to starting or reprobeing the remoteproc device, driver lifecycle control, or platform device management. Those operations are normally host-administrator or device-management operations. HostAdminRequired is set to YES because the complete practical trigger is administrative remoteproc/device lifecycle control, not an ordinary local user API. NamespaceScopedPrivilege is NO because there is no evidence that this platform remoteproc operation is available through attacker-created namespaces. No prior network exposure is involved. Special Qualcomm ADSP hardware or platform support is required, but this is not scored as a separate rare-hardware penalty because the issue is already low and platform-specific. Race repeatability is not relevant. This is an ordered missing-release bug, not a timing race. 4. Primitive and severity interpretation The exact primitive is a persistent OF device-node reference leak caused by missing `of_node_put(args.np)` after `of_parse_phandle_with_args()`. This is not active structured stale-object use and not fixed stale storage UAF. It is a resource/lifetime cleanup defect. There is no concrete repeated release/refcount operation. The first lifetime operation is missing, so no object is freed and then reused. The demonstrated consequence is resource leakage. The speculative consequence is resource exhaustion after repeated privileged lifecycle operations. PrimitiveClass is NONE because no meaningful corruption, UAF, authorization bypass, COW violation, or security-boundary primitive is established. ImportantCandidate is NO because the issue is resource leakage only and lacks unresolved exploitation leverage beyond DoS-style accumulation. AutoDowngradeAllowed is YES because automatic closure or deferred handling is reasonable for this low-risk, admin-triggered leak absent additional advisory evidence. Likely operational severity is Low to ordinary Moderate. 5. One-sentence report phrase A missing of_node_put in qcom_q6v5_adsp leaks an OF device node reference during ADSP carveout setup, requiring host administrative remoteproc or device lifecycle control to trigger and causing only potential resource exhaustion rather than memory corruption or privilege escalation. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch establishes only a missing reference release with no UAF, double put, crash primitive, network trigger, confidentiality impact, integrity impact, or privilege-escalation path. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: remoteproc: qcom_q6v5_adsp: Fix reference leak for device node [ Upstream Commit: a73cfa80f1ec6b0f948cf3c91455c62423747b3e Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a73cfa80f1ec6b0f948cf3c91455c62423747b3e Changed files: drivers/remoteproc/qcom_q6v5_adsp.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=a73cfa80f1ec6b0f948cf3c91455c62423747b3e ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93126 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93126 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:L/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.4 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).