From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-53305][LOW] usb: typec: ps883x: Fix Oops at unbind [ Upstream Date: Fri, 26 Jun 2026 16:08:58 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-53305 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: 0 X-AL-KERNEL-Commit: 37a3d1b6827783f26d2f8e6c7683e253ba79ae93 List-Id: CVE: CVE-2026-53305 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: usb: typec: ps883x: Fix Oops at unbind [ Upstream Commit: 37a3d1b6827783f26d2f8e6c7683e253ba79ae93 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=37a3d1b6827783f26d2f8e6c7683e253ba79ae93 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53305 Analysis date: Fri, 26 Jun 2026 16:08:58 -0400 ActionableScore: 1 ActionableScore lower bound: 0 Actionable bucket: Ordinary Moderate / Low-like auto-close candidate Manual review required: NO Summary: A missing `i2c_set_clientdata()` in the ps883x Type C retimer probe path can cause a NULL pointer dereference and kernel Oops during local driver unbind, typically requiring administrative device-management access and resulting in DoS only. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53305 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53305 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-53305 LOW CHECK Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-665;CWE-754;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference in the ps883x Type C retimer driver can occur because probe allocates the retimer state but does not store it as I2C client data. During driver unbind or device removal ps883x_retimer_remove calls i2c_get_clientdata() and can receive NULL, causing an Oops when the remove path dereferences the missing state. For the CVSS the PR:L is used in the paranoid score to cover deployments where a reduced capability root, service account, or delegated device management path can trigger sysfs driver unbind. The issue is not network reachable and requires local control over device unbind or removal operations. Impact is denial of service via kernel crash only, with no evidence of UAF, OOB access, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like auto-close candidate (with actual score 1) SKIP CVE-2026-53305 SKIP No affected files built, so skip this CVE NO - - unknown MAYBE OOB NULLPTR USB TIMER HARDWARE LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 ActionableScoreLower=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate / Low-like auto-close candidate**:: ## 2. Signal breakdown Triggered signals: * Reliable kernel crash / strong DoS: +1 The commit shows a real Oops caused by NULL pointer dereference in `ps883x_retimer_remove()` during driver unbind. Paranoid-only interpretation: * Local low-privileged trigger: +1 Only if a reduced-privilege service account, privileged container, or delegated device-management path can write to the relevant sysfs unbind interface. Negative signals: * Requires admin/root in typical deployments: -2 Writing to `/sys/bus/.../driver/unbind` normally requires host-root or equivalent administrative control. * Rare hardware/device-specific path: -1 The affected code is specific to the Parade PS883x Type-C retimer driver and requires such hardware/device binding. Not counted: * No generic memory corruption. This is a NULL pointer dereference, not UAF, double-free, OOB write, or type confusion. * No privilege escalation plausible from the patch. * No confidentiality or integrity impact. * No network reachability. ## 3. Reachability analysis The bug is triggered locally through driver unbind or device removal. In normal deployments this requires administrative access to sysfs device-management interfaces. Containers or namespaces do not normally make this reachable unless host device sysfs access is explicitly delegated or the container is privileged. The affected path is hardware-specific and depends on the PS883x Type-C retimer driver being present and bound. ## 4. Severity interpretation This behaves like an ordinary Moderate or Low-like local DoS issue. The failure mode is a deterministic NULL pointer dereference during remove/unbind because probe never stored driver data with `i2c_set_clientdata()`. There is no evidence of attacker-controlled object reuse, stale pointer lifetime corruption, write primitive, information leak, or privilege escalation. The paranoid score only accounts for unusual delegated device-management environments, not a stronger vulnerability class. ## 5. One-sentence report phrase A missing `i2c_set_clientdata()` in the ps883x Type C retimer probe path can cause a NULL pointer dereference and kernel Oops during local driver unbind, typically requiring administrative device-management access and resulting in DoS only. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This can be auto-closed for most triage workflows because it is a hardware-specific, local, admin-triggered NULL dereference with no supported memory-corruption or privilege-escalation primitive. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: usb: typec: ps883x: Fix Oops at unbind [ Upstream Commit: 37a3d1b6827783f26d2f8e6c7683e253ba79ae93 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=37a3d1b6827783f26d2f8e6c7683e253ba79ae93 Changed files: drivers/usb/typec/mux/ps883x.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=37a3d1b6827783f26d2f8e6c7683e253ba79ae93 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53305 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53305 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:H The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.5 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: 0 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).