# CVE-2026-80867: alpha/PCI: Add security_locked_down() check to pci_mmap_resource()

> Local attackers can bypass kernel lockdown restrictions on Alpha architecture to access PCI BARs, potentially enabling DMA attacks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** BELL-CVE-2026-80867, DEBIAN-CVE-2026-80867, GHSA-6r46-6gmq-67cv, UBUNTU-CVE-2026-80867

## What is CVE-2026-80867?

CVE-2026-80867 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

alpha/PCI: Add security_locked_down() check to pci_mmap_resource()

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().

## Which versions are affected by CVE-2026-80867?


## How do I fix CVE-2026-80867?

Apply the vendor's patch.

## Is CVE-2026-80867 being exploited?

There is no known exploitation of CVE-2026-80867 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80867 and fix it if it is affected.

What it is: CVE-2026-80867 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80867 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80867/ (Markdown: https://insights.sbomify.com/CVE-2026-80867/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80867
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80867
- OSV: https://osv.dev/vulnerability/CVE-2026-80867

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80867/
Summaries are generated and may contain mistakes; the official description above is the record.