CVE-2025-21902 Details
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.
A vulnerability has been identified in the Linux kernel's ACPI backend for UCSI, specifically related to how the UCSI 'registers' are managed. The issue arises because the ACPI implementation in the BIOS is supposed to synchronize the opregion contents with the embedded controller. However, this synchronization can be problematic on certain ACPI implementations. The vulnerability involves an improper handling of the CCI registers, leading to a spurious assertion warning. To address this, a new 'poll_cci' method has been introduced, which forces a synchronization before polling the CCI, ensuring proper register management when notifications are disabled.
Users can update to the latest version of the Linux kernel where this vulnerability has been addressed. The specific commit introducing the fix can be found in the Linux kernel Git repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/012b98cdb54c7d47743ee7fc402fa23f2d90529a | kernel.org | Patch |
| https://git.kernel.org/stable/c/1aec5c9066965ac0984e385bbc31455ae31cbffc | kernel.org | Patch |
| https://git.kernel.org/stable/c/976e7e9bdc7719a023a4ecccd2e3daec9ab20a40 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12.5, < 6.12.19 >= 6.13, < 6.13.7 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc4 6.14 rc5 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 31, 2025 | Initial Analysis | [email protected] |
| Apr 1, 2025 | New CVE Received | kernel.org |