CVE-2024-53149

USB-C disruption via off-by-one connector check

Published Dec 24, 2024 · Updated May 11, 2026

Off-by-one error in Linux 6.10 and later affected branches allows physically proximate attackers to disrupt USB-C connectivity. The pmic_glink_ucsi_connector_status() callback rejects valid connector number 3 at the PMIC_GLINK_MAX_PORTS bound, so it never updates that port's Type-C orientation. The flaw requires a Qualcomm PMIC GLINK UCSI system with a third USB-C connector; no data disclosure or modification is reported.

CVSS severity4.6
Medium
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Off-by-one error in Linux 6.10 and later affected branches allows physically proximate attackers to disrupt USB-C connectivity. The pmic_glink_ucsi_connector_status() callback rejects valid connector number 3 at the PMIC_GLINK_MAX_PORTS bound, so it never updates that port's Type-C orientation. The flaw requires a Qualcomm PMIC GLINK UCSI system with a third USB-C connector; no data disclosure or modification is reported.

The record

CVE
CVE-2024-53149
Published
Dec 24, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-193
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 24, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.10
  2. Affected versionversion=76716fd5bf09725c2c6825264147f16c21e56853 <4a22918810980897393fa1776ea3877e4baf8cca
  3. Affected versionversion=76716fd5bf09725c2c6825264147f16c21e56853 <6ba6f7f29e0dff47a2799e60dcd1b5c29cd811a5
  4. Affected versionversion=76716fd5bf09725c2c6825264147f16c21e56853 <9a5a8b5bd72169aa7a8ec800ef57be2f2cb4d9b2
  5. Affected versionversion=fd662c37a1087a2631cd2544138650b153e65f90 <8a2273e5c1beb285729aa001422967b4711c53fe

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.10; version=76716fd5bf09725c2c6825264147f16c21e56853 <4a22918810980897393fa1776ea3877e4baf8cca; version=76716fd5bf09725c2c6825264147f16c21e56853 <6ba6f7f29e0dff47a2799e60dcd1b5c29cd811a5; version=76716fd5bf09725c2c6825264147f16c21e56853 <9a5a8b5bd72169aa7a8ec800ef57be2f2cb4d9b2; version=fd662c37a1087a2631cd2544138650b153e65f90 <8a2273e5c1beb285729aa001422967b4711c53fe

Published CVSS scores

4.6NIST NVDCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-193Off-by-one Error

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo