CVE-2024-53149

What it actually does

Off-by-one error in pmic_glink_ucsi_connector_status() allows incorrect bounds check on UCSI connector indices (1 to PMIC_GLINK_MAX_PORTS), causing improper Type-C orientation reporting specifically for the third connector.

Why it matters to the business

Linux systems with multiple USB-C ports may experience unreliable hardware port behavior and orientation detection, potentially disrupting peripheral connectivity on affected kernels; low exploitability reduces urgency but patching remains necessary for hardware correctness.

How an attack unfolds

An attacker with local access or the ability to trigger connector status events could cause the callback to mishandle the third port due to the indexing error, though no public exploits or specific threat actor campaigns targeting this flaw have been observed.

How to fix it

Update the Linux kernel to the fixed commit 8a2273e5c1beb285729aa001422967b4711c53fe or later stable releases containing the patch; apply vendor backports for supported distributions.

How to confirm the fix worked

Verify kernel source contains the corrected bounds check in pmic_glink_ucsi_connector_status(); confirm running kernel version includes the referenced commit or equivalent distribution update.

Typical attack path

1. Gain local access or ability to stimulate USB-C connector events on target system
2. Trigger pmic_glink_ucsi_connector_status() callback with conditions hitting the off-by-one boundary
3. Observe or induce incorrect orientation reporting on the third connector

How to detect it

Review kernel logs for USB Type-C or UCSI glink errors around connector status events; no widespread exploitation indicators reported.

What your security team should do

• Apply the kernel fix during next maintenance window given low EPSS and absence from KEV
• Monitor for any future EPSS increases or exploit maturity changes
• Audit systems using UCSI glink drivers for third-port USB-C functionality issues