Look up another CVE · open CVE-2026-80867 in the interactive tracker
CVE-2026-80867
alpha/PCI: Add security_locked_down() check to pci_mmap_resource()
Published 2026-09-04 (44 days ago) by the Linux kernel CNA. Subsystem arch/alpha. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80867 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Currently, Alpha's pci_mmap_resource() does not check security_locked_down(LOCKDOWN_PCI_ACCESS) before allowing userspace to mmap PCI BARs. The generic version has had this check since commit eb627e17727e ("PCI: Lock down BAR access when the kernel is locked down") to prevent DMA attacks when the kernel is locked down. Add the same check to Alpha's pci_mmap_resource().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
arch/alpha/kernel/pci-sysfs.c
- What this is
- ALPHA PORTMAINTAINERS section matched on arch/alpha/ · linux-alpha@vger.kernel.org · Odd Fixes
Check it on the machine
grep -w CONFIG_PCI /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormy
- trixieYnot built on armel/rpi
- forky, sidy
- y
- built into the kernel image on every flavour - only a patch removes it
- Y
- built in where it is built at all; some flavours do not build it
- Build switch
- CONFIG_PCI
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-04 (44 days ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.22%, higher than 11.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- arch/alpha
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.4 | 5.10.261 | 6e368485a1ac |
| 5.4 | 5.15.212 | ed2cd1fee0ed |
| 5.4 | 6.1.178 | c3234efe21d4 |
| 5.4 | 6.6.145 | 4de5ff924c0a |
| 5.4 | 6.12.97 | 85f966b11208 |
| 5.4 | 6.18.40 | 94defb18ac79 |
| 5.4 | 7.1.5 | 257b55dc3d18 |
| 5.4 | 7.2 | 78a228f0aa0e |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-80867, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.