linux-cve-announce - CVE-2023-53168: usb: ucsi_acpi: Increase the command completion timeout

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091554-CVE-2023-53168-7628@gregkh>
Date: Mon, 15 Sep 2025 16:02:22 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53168: usb: ucsi_acpi: Increase the command completion timeout

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

usb: ucsi_acpi: Increase the command completion timeout

Commit 130a96d698d7 ("usb: typec: ucsi: acpi: Increase command
completion timeout value") increased the timeout from 5 seconds
to 60 seconds due to issues related to alternate mode discovery.

After the alternate mode discovery switch to polled mode
the timeout was reduced, but instead of being set back to
5 seconds it was reduced to 1 second.

This is causing problems when using a Lenovo ThinkPad X1 yoga gen7
connected over Type-C to a LG 27UL850-W (charging DP over Type-C).

When the monitor is already connected at boot the following error
is logged: "PPM init failed (-110)", /sys/class/typec is empty and
on unplugging the NULL pointer deref fixed earlier in this series
happens.

When the monitor is connected after boot the following error
is logged instead: "GET_CONNECTOR_STATUS failed (-110)".

Setting the timeout back to 5 seconds fixes both cases.

The Linux kernel CVE team has assigned CVE-2023-53168 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 5.16 with commit e08065069fc7b074712378a95a3522d557e9bbe1 and fixed in 6.1.22 with commit 1e8525f37871741a52370627633962f8bdcab15a
	Issue introduced in 5.16 with commit e08065069fc7b074712378a95a3522d557e9bbe1 and fixed in 6.2.9 with commit 8346d21d1d8a63f46f60e6899f4f80b1306acf32
	Issue introduced in 5.16 with commit e08065069fc7b074712378a95a3522d557e9bbe1 and fixed in 6.3 with commit 02d210f434249a7edbc160969b75df030dc6934d

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53168
will be updated if fixes are backported, please check that for the most
up to date information about this issue.

Affected files
==============

The file(s) affected by this issue are:
	drivers/usb/typec/ucsi/ucsi_acpi.c

Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/1e8525f37871741a52370627633962f8bdcab15a
	https://git.kernel.org/stable/c/8346d21d1d8a63f46f60e6899f4f80b1306acf32
	https://git.kernel.org/stable/c/02d210f434249a7edbc160969b75df030dc6934d