linux-cve-announce - CVE-2025-21831: PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1

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: <2025030634-CVE-2025-21831-3ada@gregkh>
Date: Thu,  6 Mar 2025 17:22:37 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21831: PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1

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

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

PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1

commit 9d26d3a8f1b0 ("PCI: Put PCIe ports into D3 during suspend") sets the
policy that all PCIe ports are allowed to use D3.  When the system is
suspended if the port is not power manageable by the platform and won't be
used for wakeup via a PME this sets up the policy for these ports to go
into D3hot.

This policy generally makes sense from an OSPM perspective but it leads to
problems with wakeup from suspend on the TUXEDO Sirius 16 Gen 1 with a
specific old BIOS. This manifests as a system hang.

On the affected Device + BIOS combination, add a quirk for the root port of
the problematic controller to ensure that these root ports are not put into
D3hot at suspend.

This patch is based on

  https://lore.kernel.org/linux-pci/20230708214457.1229-2-mario.limonciello@amd.com

but with the added condition both in the documentation and in the code to
apply only to the TUXEDO Sirius 16 Gen 1 with a specific old BIOS and only
the affected root ports.

The Linux kernel CVE team has assigned CVE-2025-21831 to this issue.

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

	Issue introduced in 4.8 with commit 9d26d3a8f1b0c442339a235f9508bdad8af91043 and fixed in 6.6.78 with commit 8852e056e297df1d8635ee7504e780d3184e45d0
	Issue introduced in 4.8 with commit 9d26d3a8f1b0c442339a235f9508bdad8af91043 and fixed in 6.12.14 with commit 5ee3dd6e59b834e4d66e8b16fc684749ee40a257
	Issue introduced in 4.8 with commit 9d26d3a8f1b0c442339a235f9508bdad8af91043 and fixed in 6.13.3 with commit a78dfe50fffe6058afed2bb04c50c2c9a16664ee
	Issue introduced in 4.8 with commit 9d26d3a8f1b0c442339a235f9508bdad8af91043 and fixed in 6.14-rc1 with commit b1049f2d68693c80a576c4578d96774a68df2bad

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-2025-21831
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:
	arch/x86/pci/fixup.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/8852e056e297df1d8635ee7504e780d3184e45d0
	https://git.kernel.org/stable/c/5ee3dd6e59b834e4d66e8b16fc684749ee40a257
	https://git.kernel.org/stable/c/a78dfe50fffe6058afed2bb04c50c2c9a16664ee
	https://git.kernel.org/stable/c/b1049f2d68693c80a576c4578d96774a68df2bad