<?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 18:12:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90315 — PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90315</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/sysfs: Add lockdown checks to legacy I/O and memory handlers&lt;/p&gt;
&lt;p&gt;Currently, the legacy I/O and memory sysfs handlers do not check
security_locked_down(LOCKDOWN_PCI_ACCESS), leaving the legacy_io and
legacy_mem files unprotected when the kernel is locked down.&lt;/p&gt;
&lt;p&gt;Commit eb627e17727e (&amp;#34;PCI: Lock down BAR access when the kernel is locked
down&amp;#34;) added the check to pci_write_config(), pci_mmap_resource(), and
pci_write_resource_io() to prevent userspace from programming DMA-capable
hardware that could be used to modify kernel code, but did not cover the
legacy handlers.&lt;/p&gt;
&lt;p&gt;As a result, root can still write arbitrary I/O ports and map the legacy
I/O and memory spaces while the kernel is locked down, which is the same
capability the lockdown is meant to remove.&lt;/p&gt;
&lt;p&gt;Add the same check to pci_write_legacy_io(), pci_mmap_legacy_mem(), and
pci_mmap_legacy_io().&lt;/p&gt;
&lt;p&gt;These generic handlers cover both architectures that define HAVE_PCI_LEGACY
(such as Alpha and PowerPC).&lt;/p&gt;
&lt;p&gt;[bhelgaas: add Link]&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/sysfs: Add lockdown checks to legacy I/O and memory handlers&lt;/p&gt;
&lt;p&gt;Currently, the legacy I/O and memory sysfs handlers do not check
security_locked_down(LOCKDOWN_PCI_ACCESS), leaving the legacy_io and
legacy_mem files unprotected when the kernel is locked down.&lt;/p&gt;
&lt;p&gt;Commit eb627e17727e (&amp;#34;PCI: Lock down BAR access when the kernel is locked
down&amp;#34;) added the check to pci_write_config(), pci_mmap_resource(), and
pci_write_resource_io() to prevent userspace from programming DMA-capable
hardware that could be used to modify kernel code, but did not cover the
legacy handlers.&lt;/p&gt;
&lt;p&gt;As a result, root can still write arbitrary I/O ports and map the legacy
I/O and memory spaces while the kernel is locked down, which is the same
capability the lockdown is meant to remove.&lt;/p&gt;
&lt;p&gt;Add the same check to pci_write_legacy_io(), pci_mmap_legacy_mem(), and
pci_mmap_legacy_io().&lt;/p&gt;
&lt;p&gt;These generic handlers cover both architectures that define HAVE_PCI_LEGACY
(such as Alpha and PowerPC).&lt;/p&gt;
&lt;p&gt;[bhelgaas: add Link]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90315</guid>
    </item>
  </channel>
</rss>
