<?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://cve.radiocsirt.org</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>Mon, 05 Oct 2026 12:37:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47333 — misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47333</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;misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge&lt;/p&gt;
&lt;p&gt;There is an issue with the ASPM(optional) capability checking function.
A device might be attached to root complex directly, in this case,
bus-&amp;gt;self(bridge) will be NULL, thus priv-&amp;gt;parent_pdev is NULL.
Since alcor_pci_init_check_aspm(priv-&amp;gt;parent_pdev) checks the PCI link&amp;#39;s
ASPM capability and populate parent_cap_off, which will be used later by
alcor_pci_aspm_ctrl() to dynamically turn on/off device, what we can do
here is to avoid checking the capability if we are on the root complex.
This will make pdev_cap_off 0 and alcor_pci_aspm_ctrl() will simply
return when bring called, effectively disable ASPM for the device.&lt;/p&gt;
&lt;p&gt;[    1.246492] BUG: kernel NULL pointer dereference, address: 00000000000000c0
[    1.248731] RIP: 0010:pci_read_config_byte+0x5/0x40
[    1.253998] Call Trace:
[    1.254131]  ? alcor_pci_find_cap_offset.isra.0+0x3a/0x100 [alcor_pci]
[    1.254476]  alcor_pci_probe+0x169/0x2d5 [alcor_pci]&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;misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge&lt;/p&gt;
&lt;p&gt;There is an issue with the ASPM(optional) capability checking function.
A device might be attached to root complex directly, in this case,
bus-&amp;gt;self(bridge) will be NULL, thus priv-&amp;gt;parent_pdev is NULL.
Since alcor_pci_init_check_aspm(priv-&amp;gt;parent_pdev) checks the PCI link&amp;#39;s
ASPM capability and populate parent_cap_off, which will be used later by
alcor_pci_aspm_ctrl() to dynamically turn on/off device, what we can do
here is to avoid checking the capability if we are on the root complex.
This will make pdev_cap_off 0 and alcor_pci_aspm_ctrl() will simply
return when bring called, effectively disable ASPM for the device.&lt;/p&gt;
&lt;p&gt;[    1.246492] BUG: kernel NULL pointer dereference, address: 00000000000000c0
[    1.248731] RIP: 0010:pci_read_config_byte+0x5/0x40
[    1.253998] Call Trace:
[    1.254131]  ? alcor_pci_find_cap_offset.isra.0+0x3a/0x100 [alcor_pci]
[    1.254476]  alcor_pci_probe+0x169/0x2d5 [alcor_pci]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47333</guid>
    </item>
  </channel>
</rss>
