Skip to main content
VulnerabilityPublished Updated

CVE-2026-80867: Linux kernel · alpha/PCI: Add security_locked_down() check to pci_mmap_resource()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ed2cd1fee0ed16a1c2dff49175e65c641eb8ae2b : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:34 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ed2cd1fee0ed16a1c2dff49175e65c641eb8ae2b, c3234efe21d4198945492cf7dba6859476f0f6ff, 257b55dc3d18d7ef01f62a8ff7317871f7597e28 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ eb627e17727ebeede70697ae1798688b0d328b54, < ed2cd1fee0ed16a1c2dff49175e65c641eb8ae2b
Fixed in
  • ed2cd1fee0ed16a1c2dff49175e65c641eb8ae2b
LinuxLinuxAffected
  • ≥ eb627e17727ebeede70697ae1798688b0d328b54, < c3234efe21d4198945492cf7dba6859476f0f6ff
Fixed in
  • c3234efe21d4198945492cf7dba6859476f0f6ff
LinuxLinuxAffected
  • ≥ eb627e17727ebeede70697ae1798688b0d328b54, < 257b55dc3d18d7ef01f62a8ff7317871f7597e28
Fixed in
  • 257b55dc3d18d7ef01f62a8ff7317871f7597e28
LinuxLinuxAffected
  • ≥ eb627e17727ebeede70697ae1798688b0d328b54, < 94defb18ac792fd16407d5a52ad0d3f5055c4b43
Fixed in
  • 94defb18ac792fd16407d5a52ad0d3f5055c4b43
LinuxLinuxAffected
  • ≥ eb627e17727ebeede70697ae1798688b0d328b54, < 85f966b1120874fe530edec50d28373ceb06ebcd
Fixed in
  • 85f966b1120874fe530edec50d28373ceb06ebcd
LinuxLinuxAffected
  • ≥ eb627e17727ebeede70697ae1798688b0d328b54, < 78a228f0aa0e9eba31955950c8a40a9945e2c8bb
Fixed in
  • 78a228f0aa0e9eba31955950c8a40a9945e2c8bb

AI-suggested

A fix has been implemented and merged into the Linux kernel source, adding the security_locked_down() check to pci_mmap_resource() for Alpha. Systems running the affected version (=5.4) should update to a kernel including the fix identified by the listed commit hashes. No additional mitigation is required once the patch is applied.

Description

A vulnerability in the Linux kernel's Alpha architecture PCI subsystem allowed userspace to mmap PCI BARs without checking the kernel lockdown state. This missing check could enable unauthorized access to PCI resources when the kernel lockdown mode is enabled. The issue has been fixed by adding the security_locked_down() check to pci_mmap_resource() for Alpha, aligning it with the generic PCI implementation.

References

Community reviews

Loading reviews…