CVE-2023-53446
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.11 (inc) to 5.4.251 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.188 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.121 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.39 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.3.13 (exc) |
| linux | linux_kernel | From 6.4 (inc) to 6.4.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free issue in the Linux kernel related to PCI/ASPM (Active State Power Management). Specifically, when a multi-function device's function 0 is removed, a pointer (pcie_link_state->downstream) to that function's pci_dev was retained. Later changes to ASPM policy would dereference this now-invalid pointer, causing a use-after-free error detected by KASAN (Kernel Address Sanitizer). The fix disables ASPM and frees the pcie_link_state when any child function is removed, preventing the dangling pointer and ensuring consistent ASPM control across all functions.
How can this vulnerability impact me? :
This vulnerability can lead to kernel instability or crashes due to use-after-free errors when managing PCIe device power states. Such instability could affect system reliability and potentially cause denial of service or unexpected behavior in systems using affected Linux kernel versions.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing use-after-free warnings from KASAN related to PCIe ASPM policy changes. For example, running commands that remove a PCI device function and then change the ASPM policy may trigger the warning. A suggested command sequence to detect the issue is: # echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove # echo powersave > /sys/module/pcie_aspm/parameters/policy If a KASAN slab-use-after-free warning appears in the kernel logs, it indicates the presence of this vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the patch that disables ASPM and frees the pcie_link_state when any child function is removed. This prevents use-after-free by discarding the dangling pointer and maintaining consistent ASPM Control configuration. Until the patch is applied, avoid removing PCI functions and changing ASPM policy dynamically to prevent triggering the vulnerability.