LiveActive security incident?Get immediate response
CVE Record

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]

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
high
Sources
9

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-53446 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-53446Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb5a0a9b59c8185aebcd9a717e2e6258b58c72c06, b5a0a9b59c8185aebcd9a717e2e6258b58c72c06, b5a0a9b59c8185aebcd9a717e2e6258b58c72c06, b5a0a9b59c8185aebcd9a717e2e6258b58c72c06, b5a0a9b59c8185aebcd9a717e2e6258b58c72c06, b5a0a9b59c8185aebcd9a717e2e6258b58c72c06, b5a0a9b59c8185aebcd9a717e2e6258b58c72c06unaffected
LinuxLinux4.11, 0, 5.4.251, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

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.