[CVE-2026-53028][LOW] usb: typec: Fix error pointer dereference [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-53028
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: usb: typec: Fix error pointer dereference [ Upstream
Commit: 19951118fb22b5ad512379ee64510fe0e2c40eb3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=19951118fb22b5ad512379ee64510fe0e2c40eb3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53028
Analysis date: Fri, 26 Jun 2026 12:29:20 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like. Auto-close candidate after normal patch intake
Manual review required: NO

Summary:
An ERR_PTR dereference in the USB Type-C tipd CD321x update path can crash the kernel if partner registration fails and identity handling continues, but exploitation appears limited to physical or firmware-mediated DoS with no supported confidentiality, integrity, or privilege-escalation impact.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53028 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53028

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-53028	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-252;CWE-703;Other CVSS 'AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.6';DESCR 'An ERR_PTR dereference can occur in the USB Type-C tipd driver because typec_register_partner can fail and cd321x_update_work continues after only logging a warning. If identity data is present, typec_partner_set_identity may then receive the ERR_PTR partner value and the kernel can crash. For the CVSS the PR:N is used because a physical attacker or attached Type-C device does not need privileges on the victim system. The issue is not network reachable and is tied to local hardware or physical USB Type-C interaction. Impact is denial of service only via kernel oops or panic, with no supported confidentiality or integrity impact from the patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like. Auto-close candidate after normal patch intake (with actual score 1) 	MAYBE	USB 	-	-	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 after normal patch intake**

## 2. Signal breakdown

Triggered signals:

* Firmware-mediated external influence: +1
  A physically attached USB Type-C device or controller state may influence partner registration and identity handling.

* Reliable kernel crash / strong DoS: +1
  If `typec_register_partner()` returns `ERR_PTR()` and `desc.identity` is set, the driver may pass an error pointer to `typec_partner_set_identity()`, causing an oops or panic.

* Physical-only or rare hardware-only condition: -2
  This is tied to USB Type-C hardware interaction and the `tipd` CD321x path, not a network or generic local syscall interface.

Conservative interpretation also treats the trigger as hardware and error-state dependent, so the effective score is capped at 0. Paranoid interpretation gives credit for a possible externally influenced crash and results in 1.

Not triggered:

* No generic memory corruption. This is an `ERR_PTR` dereference, not UAF, double-free, OOB write, or controlled overwrite.
* No privilege escalation plausible from the patch context.
* No confidentiality or integrity impact is supported.
* No network reachability.
* No namespace or container boundary bypass.

## 3. Reachability analysis

The likely trigger is a physical or firmware-mediated USB Type-C event on systems using the affected `tipd` CD321x driver path. A local unprivileged user is not clearly able to trigger this through a normal kernel data-plane API. A physically attached device may influence the Type-C state, but the crash also depends on `typec_register_partner()` failing while identity data is present.

Namespaces and containers do not materially lower the privilege requirement because the vulnerable path is hardware and driver-event driven, not exposed through a namespaced syscall or netlink control plane. The affected subsystem is common enough on some laptops and USB-C systems, but this specific driver path and failure condition are hardware dependent.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like kernel DoS issue. The theoretical impact is a host crash through an invalid error-pointer dereference. There is no realistic evidence of a memory corruption primitive, object lifetime control, attacker-controlled overwrite, information disclosure, or privilege escalation.

The paranoid score remains low because the strongest defensible interpretation is physical or firmware-mediated denial of service.

## 5. One-sentence report phrase

An ERR_PTR dereference in the USB Type-C tipd CD321x update path can crash the kernel if partner registration fails and identity handling continues, but exploitation appears limited to physical or firmware-mediated DoS with no supported confidentiality, integrity, or privilege-escalation impact.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: this is a physical or hardware-dependent DoS-only issue with low actionable score, no memory corruption primitive, no network reachability, and no plausible privilege escalation path from the patch context.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: usb: typec: Fix error pointer dereference [ Upstream
Commit: 19951118fb22b5ad512379ee64510fe0e2c40eb3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=19951118fb22b5ad512379ee64510fe0e2c40eb3

Changed files:
  drivers/usb/typec/tipd/core.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=19951118fb22b5ad512379ee64510fe0e2c40eb3

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53028 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53028

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:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.6

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).