From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-93225][LOW] phy: fsl-imx8mq-usb: fix typec switch leak on probe error path Date: Thu, 24 Sep 2026 12:21:56 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-93225 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: 1 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: f1b7b2c7ffa9711d1298f52790b377fe02efc1db List-Id: CVE: CVE-2026-93225 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: phy: fsl-imx8mq-usb: fix typec switch leak on probe error path Commit: f1b7b2c7ffa9711d1298f52790b377fe02efc1db Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f1b7b2c7ffa9711d1298f52790b377fe02efc1db Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93225 Analysis date: Thu, 24 Sep 2026 12:21:56 -0400 ActionableScore: 1 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-93225 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93225 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-93225 LOW https://www.kernelcve.org/list/?q=CVE-2026-93225 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-401;*CWE-772;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N';BEST CVSS score: '1.9';DESCR 'A typec switch registered during IMX95 USB PHY initialization is not released if driver probe fails after TCA initialization. Repeated failed probe attempts could retain kernel resources and associated memory, but the patch context does not show a use after free, invalid memory access, information disclosure, or privilege escalation primitive. For the CVSS the PR:H because reliably triggering repeated driver probe failures normally requires administrative control over the affected device, driver, or platform configuration. The issue is not network reachable. The realistic impact is a local resource leak and not an immediate system crash.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) YES USB INIT SIMPLEFIX LEAK ERRORPATH HARDWARE LINUS YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Concrete persistent kernel resource/reference leak. `typec_switch_register()` succeeds, but on a later probe failure the registered Type-C switch is not released because the former cleanup existed only in the driver remove path. * No reliable kernel crash or host-wide DoS point. The supplied patch establishes a leaked registration/resource, not a crash, invalid dereference, or exhaustion event. * No UAF, double release, refcount mutation, OOB access, arbitrary write, controlled reclaim, or stale-object use is established. * No confidentiality or integrity point. No disclosure, unauthorized modification, policy bypass, or privilege escalation primitive is shown. * No remote-reachability point. This is a local platform-driver probe lifecycle path. * No host-admin penalty is applied. Administrative control is plausible for reliably forcing repeated probe failures, but the supplied evidence does not positively establish the complete privilege boundary. * No niche hardware penalty is applied. The driver is hardware-specific, but no evidence proves that this should reduce the security assessment further. 3. Reachability analysis The leak occurs when the IMX95 USB PHY platform-driver probe fails after Type-C switch registration. Triggering the relevant failure requires the affected platform device and a probe-error condition after `imx95_usb_phy_get_tca()` succeeds. The supplied patch does not establish that an ordinary local user, a namespace-scoped capability holder, or a remote party can create the platform device, force reprobe, or reliably induce the required error path. It also does not prove that host-administrator-equivalent privilege is always required. Therefore HostAdminRequired and NamespaceScopedPrivilege remain UNKNOWN. No network, firmware-mediated external, or attacker-controlled data-plane trigger is established. Repeated probe failures may accumulate leaked Type-C switch resources, but repeatability and meaningful host-wide exhaustion are not demonstrated. 4. Primitive and severity interpretation The exact primitive is a missing cleanup operation for a Type-C switch registration during a platform-driver probe error path. This is a concrete resource/reference leak, not a lifetime violation caused by releasing an object too early. There is no active structured stale object, no post-free access, no destructor UAF, and no repeated release/refcount mutation. The patch changes cleanup ownership to `devm_add_action_or_reset()`, ensuring `typec_switch_unregister()` is invoked on both probe failure and normal driver removal. PrimitiveClass is NONE because no meaningful memory-corruption, authorization, ownership-boundary, or stale-lifetime primitive is established. The demonstrated consequence is retained kernel resource state after failed probe. A hypothetical consequence is gradual resource pressure after repeated failures, but the supplied evidence does not establish a reliable or host-wide denial of service. ImportantCandidate is NO because the issue is a constrained cleanup leak without unresolved corruption or security-boundary leverage. AutoDowngradeAllowed is YES because automatic lower-priority handling would not discard a concrete UAF, corruption primitive, authorization bypass, or exploitable ownership violation. 5. One-sentence report phrase A failed IMX95 USB PHY probe can leak a registered Type-C switch because cleanup was only performed during driver removal, resulting in a local resource leak without a demonstrated crash, memory corruption, or privilege-escalation primitive. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch establishes a probe-error resource leak only, with no demonstrated corruption, security-boundary bypass, remote exposure, or meaningful unresolved exploitation primitive. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: phy: fsl-imx8mq-usb: fix typec switch leak on probe error path Commit: f1b7b2c7ffa9711d1298f52790b377fe02efc1db Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f1b7b2c7ffa9711d1298f52790b377fe02efc1db Commit description: If probe fails after imx95_usb_phy_get_tca() succeeds, the typec switch leaks because the only cleanup path was in .remove(), which never runs on probe failure. Use devm_add_action_or_reset() so the switch is cleaned up on both probe failure and driver removal. The imx95_usb_phy_put_tca() is no longer needed, it will be removed in .remove() too. Fixes: b58f0f8 ("phy: fsl-imx8mq-usb: add tca function driver for imx95") Cc: stable@vger.kernel.org Reviewed-by: Frank Li Reviewed-by: Xu Yang Signed-off-by: Felix Gu Signed-off-by: Xu Yang Link: https://patch.msgid.link/20260731-imx8mp-usb-phy-improvement-v8-1-2ec8d6b3854d@nxp.com Signed-off-by: Vinod Koul Signed-off-by: Greg Kroah-Hartman Changed files: drivers/phy/freescale/phy-fsl-imx8mq-usb.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=f1b7b2c7ffa9711d1298f52790b377fe02efc1db ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-93225 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93225 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:N 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: 1 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).