dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53028

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.18.33 / 7.0.10 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: usb: typec: Fix error pointer dereference The variable tps->partner is checked for an error pointer and then if it is, it sends an error message but does not return and then immediately dereferenced a few lines below: tps->partner = typec_register_partner(tps->port, &desc); if (IS_ERR(tps->partner)) dev_warn(tps->dev, "%s: failed to register partnet\n", __func__); if (desc.identity) { typec_partner_set_identity(tps->partner); cd321x->cur_partner_identity = st.partner_identity; } Add early return and fix spelling mistake in error message. Detected by Smatch: drivers/usb/typec/tipd/core.c:827 cd321x_update_work() error: 'tps->partner' dereferencing possible ERR_PTR()

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel USB Type-C driver (drivers/usb/typec/tipd/core.c), the cd321x_update_work() function checks if typec_register_partner() returns an error pointer but fails to return early. The code prints a warning but continues execution, then dereferences tps->partner a few lines later in typec_partner_set_identity() without re-checking, causing a potential kernel NULL/dereference error when the registration fails.

MitigationApply the upstream kernel patch which adds an early return after the error pointer check and corrects the spelling error in the warning message. This is a single-point fix in a kernel driver requiring kernel rebuild and verification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.18, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected range
    Run `uname -r` or check `/proc/version` to get the running kernel version. Compare it to the affected ranges: >= 6.18, < 6.18.33 or >= 6.19, < 7.0.10
    Affected if Kernel version falls within either 6.18.x where x < 33, or 6.19.x through 7.0.x where x < 10
  2. Verify USB Type-C tipd driver is in use
    Check if the tipd driver is loaded: run `lsmod | grep -i tipd` for module, or check kernel config for `CONFIG_USB_TIPD` using `grep CONFIG_USB_TIPD /boot/config-$(uname -r)` or `/proc/config.gz`
    Affected if The tipd USB Type-C driver is compiled or loaded on the system
  3. Inspect the vulnerable source function
    Locate the file drivers/usb/typec/tipd/core.c in the kernel source tree. Search for the cd321x_update_work function and locate the typec_register_partner() call. Verify if the code lacks an early return after checking for IS_ERR on the return value before proceeding to typec_partner_set_identity()
    Affected if The source code shows typec_register_partner() error check without an immediate return, allowing execution to continue to typec_partner_set_identity()

System is affected if running a kernel in the vulnerable version range AND the USB Type-C tipd driver is present, AND the source code lacks the early return after typec_register_partner() failure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.18.33 / 7.0.10 or later
Fixed in 6.18.337.0.10
Interim mitigation

Apply the upstream kernel patch which adds an early return after the error pointer check and corrects the spelling error in the warning message. This is a single-point fix in a kernel driver requiring kernel rebuild and verification.

Recommended fix High confidence

Linux Kernel 6.18.33 or 7.0.10 (depending on which major version branch you are on)

  1. Identify the currently running kernel version using 'uname -r'
  2. If running kernel >= 6.18 and < 6.18.33, upgrade to kernel version 6.18.33 or later
  3. If running kernel >= 6.19 and < 7.0.10, upgrade to kernel version 7.0.10 or later
  4. Apply the upgrade via your distribution's package manager (e.g., 'apt-get update && apt-get upgrade' for Debian/Ubuntu, 'yum update' for RHEL/CentOS, or 'dnf upgrade' for Fedora)
  5. Reboot the system to load the fixed kernel
  6. Verify the fix is applied by checking the kernel version and reviewing the patch in drivers/usb/typec/tipd/core.c
Caveat Kernel upgrades may require rebooting services; ensure compatibility with existing system configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53028 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data