CVE-2023-53446: PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free
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]
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in PCIe power-management handling. A local user with sufficient privileges could trigger a use-after-free after PCI function removal and later ASPM policy changes. The CVSS score is high, but the source bundle does not show internet exposure or confirmed exploitation.
Executive priority
Schedule remediation in the next kernel patch cycle, faster for shared servers, developer workstations, and systems with many local users. No source confirms active exploitation, but kernel use-after-free issues can carry high business impact if reachable.
Technical view
The bug is CWE-416 in PCIe ASPM state management. When function 0 of a multi-function PCI device was removed, pcie_link_state->downstream could retain a freed pci_dev pointer. Later ASPM policy changes dereferenced it. Stable fixes disable ASPM and free pcie_link_state when any child function is removed.
Likely exposure
Exposure is limited to Linux systems running affected kernels where a local user or service can influence PCIe function removal and ASPM policy changes. Cloud guests may be less exposed unless such controls are available. Confirm against distribution backports, not only upstream version numbers.
Exploitation context
The source bundle lists KEV as false and provides no evidence of active exploitation. The described trigger is local and requires privileges according to the CVSS vector. Treat this as a serious local kernel hardening issue, not as a confirmed remote attack path.
Researcher notes
The provided evidence supports a local PCIe ASPM use-after-free with high CVSS impact. It does not prove practical privilege escalation, affected distribution packages, or exploit availability. Validation should focus on kernel lineage, stable backports, and whether the PCIe management path is reachable locally.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Prioritize multi-user Linux systems and hosts exposing PCIe management controls.
Check distribution advisories before assuming upstream version numbers are decisive.
Restrict unnecessary local access to PCIe device management interfaces.
Follow Linux kernel or vendor guidance if no packaged fix is available.
Validation and detection
Inventory running kernel versions across Linux assets.
Compare vendor kernel changelogs against the referenced stable commits.
Confirm affected systems are not relying on unfixed upstream ranges.
Review whether local users or services can manage PCIe devices or ASPM policy.
Track remediation through normal kernel patch verification and reboot evidence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.