Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < 6e368485a1ac19fbde0a8b6a332d4545ae72a8ac
    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < ed2cd1fee0ed16a1c2dff49175e65c641eb8ae2b
    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < c3234efe21d4198945492cf7dba6859476f0f6ff
    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < 4de5ff924c0a8ef8166c1a68af9087826e1e8d61
    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < 85f966b1120874fe530edec50d28373ceb06ebcd
    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < 94defb18ac792fd16407d5a52ad0d3f5055c4b43
    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < 257b55dc3d18d7ef01f62a8ff7317871f7597e28
    • affected eb627e17727ebeede70697ae1798688b0d328b54 – < 78a228f0aa0e9eba31955950c8a40a9945e2c8bb
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80867 badge
[![CVE-2026-80867](https://cveledger.app/badge/CVE-2026-80867.svg)](https://cveledger.app/cve/CVE-2026-80867)

Record last updated .