<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 15:04:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53446 — PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53446</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Struct pcie_link_state-&amp;gt;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.:&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove
  # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Disable ASPM and free the pcie_link_state when any child function is
removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer
and maintain the same ASPM Control configuration for all functions.&lt;/p&gt;
&lt;p&gt;[bhelgaas: commit log and comment]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;PCI/ASPM: Disable ASPM on MFD function removal to avoid use-after-free&lt;/p&gt;
&lt;p&gt;Struct pcie_link_state-&amp;gt;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.:&lt;/p&gt;
&lt;p&gt;# echo 1 &amp;gt; /sys/bus/pci/devices/0000:03:00.0/remove
  # echo powersave &amp;gt; /sys/module/pcie_aspm/parameters/policy&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Disable ASPM and free the pcie_link_state when any child function is
removed so we can discard the dangling pcie_link_state-&amp;gt;downstream pointer
and maintain the same ASPM Control configuration for all functions.&lt;/p&gt;
&lt;p&gt;[bhelgaas: commit log and comment]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53446</guid>
    </item>
  </channel>
</rss>
