Lockdown bypass via unchecked PCI BAR mapping
Published Sep 4, 2026 · Updated Sep 4, 2026
Improper access control in affected Alpha builds of Linux allows local users to map PCI BARs despite kernel lockdown. Alpha’s pci_mmap_resource() maps a PCI device BAR into userspace without calling security_locked_down(LOCKDOWN_PCI_ACCESS). A local user with access to a PCI resource file can bypass the lockdown policy and obtain device-memory access usable for DMA attacks.
Summary
What happened
Improper access control in affected Alpha builds of Linux allows local users to map PCI BARs despite kernel lockdown. Alpha’s pci_mmap_resource() maps a PCI device BAR into userspace without calling security_locked_down(LOCKDOWN_PCI_ACCESS). A local user with access to a PCI resource file can bypass the lockdown policy and obtain device-memory access usable for DMA attacks.
The record
- CVE
- CVE-2026-80867
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <257b55dc3d18d7ef01f62a8ff7317871f7597e28
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <4de5ff924c0a8ef8166c1a68af9087826e1e8d61
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <6e368485a1ac19fbde0a8b6a332d4545ae72a8ac
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <78a228f0aa0e9eba31955950c8a40a9945e2c8bb
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <85f966b1120874fe530edec50d28373ceb06ebcd
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <94defb18ac792fd16407d5a52ad0d3f5055c4b43
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <c3234efe21d4198945492cf7dba6859476f0f6ff
- Affected versionversion=eb627e17727ebeede70697ae1798688b0d328b54 <ed2cd1fee0ed16a1c2dff49175e65c641eb8ae2b
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo