Vulnerability · Published Apr 1, 2025 · Assigned by Linux

CVE-2025-21902acpi: typec: ucsi: Introduce a ->poll_cci method

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 88.9% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: acpi: typec: ucsi: Introduce a ->poll_cci method For the ACPI backend of UCSI the UCSI "registers" are just a memory copy of the register values in an opregion. The ACPI implementation in the BIOS ensures that the opregion contents are synced to the embedded controller and it ensures that the registers (in particular CCI) are synced back to the opregion on notifications. While there is an ACPI call that syncs the actual registers to the opregion there is rarely a need to do this and on some ACPI implementations it actually breaks in various interesting ways. The only reason to force a sync from the embedded controller is to poll CCI while notifications are disabled. Only the ucsi core knows if this is the case and guessing based on the current command is suboptimal, i.e. leading to the following spurious assertion splat: WARNING: CPU: 3 PID: 76 at drivers/usb/typec/ucsi/ucsi.c:1388 ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi] CPU: 3 UID: 0 PID: 76 Comm: kworker/3:0 Not tainted 6.12.11-200.fc41.x86_64 #1 Hardware name: LENOVO 21D0/LNVNB161216, BIOS J6CN45WW 03/17/2023 Workqueue: events_long ucsi_init_work [typec_ucsi] RIP: 0010:ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi] Call Trace: <TASK> ucsi_init_work+0x3c/0xac0 [typec_ucsi] process_one_work+0x179/0x330 worker_thread+0x252/0x390 kthread+0xd2/0x100 ret_from_fork+0x34/0x50 ret_from_fork_asm+0x1a/0x30 </TASK> Thus introduce a ->poll_cci() method that works like ->read_cci() with an additional forced sync and document that this should be used when polling with notifications disabled. For all other backends that presumably don't have this issue use the same implementation for both methods.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.19-1DEBIAN-CVE-2025-21902
Debian:14linux6.12.19-1DEBIAN-CVE-2025-21902
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1018.18~24.04.1USN-7628-1
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1018.18~24.04.1UBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1016.16~24.04.1USN-7605-1
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1016.16~24.04.1UBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-28.28~24.04.1UBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-28.28~24.04.1USN-7605-1
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1015.16~24.04.2UBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1015.16~24.04.2USN-7605-2
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1012.12UBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1021.21UBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1021.21USN-7491-1
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-21902
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-21902
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-21902

Affected products (as reported)

VendorProductVersions
Linux Linux c0ca6fd5f6ebde8fc0df8bb5c32629d1284f60d0 – before 012b98cdb54c7d47743ee7fc402fa23f2d90529afa48d7e81624efdf398b990a9049e9cd75a5aead – before 1aec5c9066965ac0984e385bbc31455ae31cbffcfa48d7e81624efdf398b990a9049e9cd75a5aead – before 976e7e9bdc7719a023a4ecccd2e3daec9ab20a406.12.5 – before 6.12.19
Linux Linux 6.13

References