CVE-2026-90315

PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers

Published Sep 17, 2026 CVSS n/a EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers

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.

Commit eb627e17727e ("PCI: Lock down BAR access when the kernel is locked
down") 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.

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.

Add the same check to pci_write_legacy_io(), pci_mmap_legacy_mem(), and
pci_mmap_legacy_io().

These generic handlers cover both architectures that define HAVE_PCI_LEGACY
(such as Alpha and PowerPC).

[bhelgaas: add Link]

Analysis

AI-generated

Technical impact

The vulnerability stems from the legacy I/O and memory sysfs handlers in the Linux kernel not performing a lockdown check (security_locked_down(LOCKDOWN_PCI_ACCESS)), which is meant to restrict hardware access when the kernel is in lockdown mode. As a result, even when the kernel is locked down, a privileged user can still write arbitrary I/O ports and map legacy I/O and memory spaces, allowing manipulation of DMA‐capable hardware and potentially modification of kernel code. This flaw undermines the intended security boundary enforced by kernel lockdown and can be abused to compromise kernel integrity.

Affected Systems

All versions of the Linux kernel that implement legacy PCI I/O and memory handlers—specifically those on architectures that define HAVE_PCI_LEGACY such as Alpha and PowerPC—are affected. The issue persists until the kernel includes the patch that adds the lockdown check to pci_write_legacy_io(), pci_mmap_legacy_mem(), and pci_mmap_legacy_io().

Risk and Exploitability

The EPSS score is reported as < 1%, indicating a very low probability of exploitation in the wild. Because the flaw only affects actions that require root privileges or a corrupting process with equivalent rights, the risk for general or remote attackers remains minimal. Nonetheless, the vulnerability demonstrates a failure of the kernel lockdown mechanism, which is critical for protecting systems that rely on this feature. The CISA KEV catalog does not list this issue, further suggesting that known exploits are not currently available.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the patch adding the lockdown check to the legacy I/O and memory handlers
  • Recompile and load the kernel module with the updated source if a packaged update is unavailable
  • If an update cannot be performed immediately, consider disabling legacy PCI I/O and memory handlers through kernel configuration or runtime parameters to reduce exposure

Generated by OpenCVE AI on September 19, 2026 at 04:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
History
Type Values Removed Values Added
First Time appeared Linux kernel
Vendors & Products Linux kernel
Type Values Removed Values Added
Weaknesses CWE-284
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers 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. Commit eb627e17727e ("PCI: Lock down BAR access when the kernel is locked down") 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. 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. Add the same check to pci_write_legacy_io(), pci_mmap_legacy_mem(), and pci_mmap_legacy_io(). These generic handlers cover both architectures that define HAVE_PCI_LEGACY (such as Alpha and PowerPC). [bhelgaas: add Link]
Title PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 9:01 AM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 17, 2026, 5:17 PM
Modified
Oct 19, 2026, 9:19 AM