CVE-2023-53446

published 18 Sep 2025 · updated 11 May 2026

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

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4203722d51afe3d239e03f15cc73efdf023a7103, Kernel 456d8aa37d0f56fc9e985e812496e861dcd6f2f2, Kernel 666e7f9d60cee23077ea3e6331f6f8a19f7ea03f and 4 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.11, >=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <4203722d51afe3d239e03f15cc73efdf023a7103, >=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <456d8aa37d0f56fc9e985e812496e861dcd6f2f2, >=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <666e7f9d60cee23077ea3e6331f6f8a19f7ea03f, >=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <7aecdd47910c51707696e8b0e045b9f88bd4230f, >=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <7badf4d6f49a358a01ab072bbff88d3ee886c33b, >=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <9856c0de49052174ab474113f4ba40c02aaee086, >=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <d51d2eeae4ce54d542909c4d9d07bf371a78592c4203722d51afe3d239e03f15cc73efdf023a7103, 456d8aa37d0f56fc9e985e812496e861dcd6f2f2, 666e7f9d60cee23077ea3e6331f6f8a19f7ea03f, 7aecdd47910c51707696e8b0e045b9f88bd4230f, 7badf4d6f49a358a01ab072bbff88d3ee886c33b, 9856c0de49052174ab474113f4ba40c02aaee086, d51d2eeae4ce54d542909c4d9d07bf371a78592c

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-53446 severity on Zeptric[![CVE-2023-53446](https://zeptric.io/badge/cve/CVE-2023-53446.svg)](https://zeptric.io/cve/CVE-2023-53446)