PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1
Summary
| CVE | CVE-2025-21831 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-03-06 17:15:23 UTC |
| Updated | 2026-11-05 21:17:43 UTC |
| 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/[email protected] 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. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: NVD-CWE-noinfo
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 9d26d3a8f1b0c442339a235f9508bdad8af91043 ff1cc51313ebe2f17530fcce0fb908cfcbbf38e5 git | Not specified |
| CNA | Linux | Linux | affected 9d26d3a8f1b0c442339a235f9508bdad8af91043 8852e056e297df1d8635ee7504e780d3184e45d0 git | Not specified |
| CNA | Linux | Linux | affected 9d26d3a8f1b0c442339a235f9508bdad8af91043 5ee3dd6e59b834e4d66e8b16fc684749ee40a257 git | Not specified |
| CNA | Linux | Linux | affected 9d26d3a8f1b0c442339a235f9508bdad8af91043 a78dfe50fffe6058afed2bb04c50c2c9a16664ee git | Not specified |
| CNA | Linux | Linux | affected 9d26d3a8f1b0c442339a235f9508bdad8af91043 b1049f2d68693c80a576c4578d96774a68df2bad git | Not specified |
| CNA | Linux | Linux | affected 4.8 | Not specified |
| CNA | Linux | Linux | unaffected 4.8 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.191 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.78 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.14 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.13.3 6.13.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.14 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/8852e056e297df1d8635ee7504e780d3184e45d0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/ff1cc51313ebe2f17530fcce0fb908cfcbbf38e5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a78dfe50fffe6058afed2bb04c50c2c9a16664ee | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/b1049f2d68693c80a576c4578d96774a68df2bad | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/5ee3dd6e59b834e4d66e8b16fc684749ee40a257 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.