diff options
| author | Krzysztof Wilczyński <kwilczynski@kernel.org> | 2026-07-20 21:15:41 +0000 |
|---|---|---|
| committer | Bjorn Helgaas <bhelgaas@google.com> | 2026-08-04 17:04:47 -0500 |
| commit | 747b9bbbbdfdee51aee2456388f9b94b5086de4d (patch) | |
| tree | f1e1eaf67b6359679a67283f6b04f93057282c40 /scripts | |
| parent | bad94d3d18c600cfe2c24c17b1825db4b8795e3e (diff) | |
| download | linux-stable-747b9bbbbdfdee51aee2456388f9b94b5086de4d.tar.gz linux-stable-747b9bbbbdfdee51aee2456388f9b94b5086de4d.zip | |
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).
Fixes: eb627e17727e ("PCI: Lock down BAR access when the kernel is locked down")
Signed-off-by: Krzysztof Wilczyński <kwilczynski@kernel.org>
[bhelgaas: add Link]
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Link: https://patch.msgid.link/20260720211541.1509744-1-kwilczynski@kernel.org
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
