Kernel memory corruption via stale PCI device pointer
Published Sep 18, 2025 · Updated Sep 18, 2025
Use-after-free in Linux kernel PCI/ASPM allows local users to trigger stale kernel-memory access after PCI function removal. The pcie_link_state->downstream field retains the removed function-zero pci_dev pointer, and a later ASPM policy change dereferences it. The demonstrated path requires permission to remove a multifunction PCIe function and change the global ASPM policy; KASAN reports the resulting invalid access.
Summary
What happened
Use-after-free in Linux kernel PCI/ASPM allows local users to trigger stale kernel-memory access after PCI function removal. The pcie_link_state->downstream field retains the removed function-zero pci_dev pointer, and a later ASPM policy change dereferences it. The demonstrated path requires permission to remove a multifunction PCIe function and change the global ASPM policy; KASAN reports the resulting invalid access.
The record
- CVE
- CVE-2023-53446
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.11
- Affected versionversion=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <4203722d51afe3d239e03f15cc73efdf023a7103
- Affected versionversion=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <456d8aa37d0f56fc9e985e812496e861dcd6f2f2
- Affected versionversion=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <666e7f9d60cee23077ea3e6331f6f8a19f7ea03f
- Affected versionversion=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <7aecdd47910c51707696e8b0e045b9f88bd4230f
- Affected versionversion=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <7badf4d6f49a358a01ab072bbff88d3ee886c33b
- Affected versionversion=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <9856c0de49052174ab474113f4ba40c02aaee086
- Affected versionversion=b5a0a9b59c8185aebcd9a717e2e6258b58c72c06 <d51d2eeae4ce54d542909c4d9d07bf371a78592c
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo