Look up another CVE · open CVE-2025-21831 in the interactive tracker
CVE-2025-21831
PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1
Published 2025-03-06 (19 months ago) by the Linux kernel CNA. Subsystem arch/x86. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2025-21831 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.12.15-1 | Update the kernel and reboot. Fixed in 6.12.15-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.12.15-1 | Update the kernel and reboot. Fixed in 6.12.15-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.12.15-1 | Update the kernel and reboot. Fixed in 6.12.15-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
arch/x86/pci/fixup.c
- What this is
- PCI SUBSYSTEMMAINTAINERS section matched on arch/x86/pci/ · linux-pci@vger.kernel.org · Supported
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidy
- y
- built into the kernel image on every flavour - only a patch removes it
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS Debian linux-config packages
Signals
- Published
- 2025-03-06 (19 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.18%, higher than 7.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- arch/x86
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.8 | 6.6.78 | 8852e056e297 |
| 4.8 | 6.12.14 | 5ee3dd6e59b8 |
| 4.8 | 6.13.3 | a78dfe50fffe |
| 4.8 | 6.14 | b1049f2d6869 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2025-21831, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.