CVE-2023-53446

PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free

HIGH
7.8
CVSS Score
Published: September 18, 2025 at 04:04 PM UTC
Updated: June 17, 2026 at 06:45 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free Struct pcie_link_state->downstream is a pointer to the pci_dev of function 0. Previously we retained that pointer when removing function 0, and subsequent ASPM policy changes dereferenced it, resulting in a use-after-free warning from KASAN, e.g.: # echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove # echo powersave > /sys/module/pcie_aspm/parameters/policy BUG: KASAN: slab-use-after-free in pcie_config_aspm_link+0x42d/0x500 Call Trace: kasan_report+0xae/0xe0 pcie_config_aspm_link+0x42d/0x500 pcie_aspm_set_policy+0x8e/0x1a0 param_attr_store+0x162/0x2c0 module_attr_store+0x3e/0x80 PCIe spec r6.0, sec 7.5.3.7, recommends that software program the same ASPM Control value in all functions of multi-function devices. Disable ASPM and free the pcie_link_state when any child function is removed so we can discard the dangling pcie_link_state->downstream pointer and maintain the same ASPM Control configuration for all functions. [bhelgaas: commit log and comment]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.11 ≤ v < 5.10.1884.11 ≤ v < 5.15.1214.11 ≤ v < 5.4.2514.11 ≤ v < 6.1.394.11 ≤ v < 6.3.134.11 ≤ v < 6.4.44.11 ≤ v < 6.55.11 ≤ v < 5.15.1215.16 ≤ v < 6.1.395.5 ≤ v < 5.10.1886.2 ≤ v < 6.3.136.4 ≤ v < 6.4.44.11b5a0a9b59c8185aebcd9a717e2e6258b58c72c06
Vendor states this is fixed in 4203722d51afe3d239e03f15cc73efdf023a7103 (fixed)
Vendor states this is fixed in 456d8aa37d0f56fc9e985e812496e861dcd6f2f2 (fixed)
Vendor states this is fixed in 666e7f9d60cee23077ea3e6331f6f8a19f7ea03f (fixed)
Vendor states this is fixed in 7aecdd47910c51707696e8b0e045b9f88bd4230f (fixed)
Vendor states this is fixed in 7badf4d6f49a358a01ab072bbff88d3ee886c33b (fixed)
Vendor states this is fixed in 9856c0de49052174ab474113f4ba40c02aaee086 (fixed)
Vendor states this is fixed in d51d2eeae4ce54d542909c4d9d07bf371a78592c (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.10.188 (unaffected)
Vendor states this is fixed in 5.15.121 (unaffected)
Vendor states this is fixed in 5.4.251 (unaffected)
Vendor states this is fixed in 6.1.39 (unaffected)
Vendor states this is fixed in 6.3.13 (unaffected)
Vendor states this is fixed in 6.4.4 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card