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-93206PCI/proc: Use file_ns_capable() when checking config space read access

Description

In the Linux kernel, the following vulnerability has been resolved: PCI/proc: Use file_ns_capable() when checking config space read access proc_bus_pci_read() decides how much of the config space is readable based on capable(CAP_SYS_ADMIN), which checks the credentials of the task calling read(), not the credentials of the process that opened the file. The sysfs equivalent, pci_read_config(), has checked the credentials of the opening process since commit de139a339395 ("pci: check caps from sysfs file open to read device dependent config space"), so a privileged process can open the config space file and pass the file descriptor to an unprivileged process (for example, a process running a KVM guest with an assigned device), which can then read the entire config space. The check was subsequently routed through the LSM framework in commit 47970b1b2aa6 ("pci: use security_capable() when checking capablities during config space read") and converted to the dedicated helper in commit ab0fa82b2df9 ("pci-sysfs: use proper file capability helper function"). Thus, the two interfaces check the same capability against different credentials. Checking the credentials of the task calling read() makes the outcome depend on who reads rather than who opened, so the restriction is bypassed whenever a more privileged process reads through the descriptor. Checking the credentials recorded in file->f_cred settles the decision at open() time and ties it to the file, where it cannot change with the caller. Use file_ns_capable() to check CAP_SYS_ADMIN against the credentials in effect when the file was opened, bringing the procfs interface in line with the sysfs behaviour. As a result, a file descriptor opened by a privileged process and passed to an unprivileged one now allows the entire config space to be read through procfs, matching sysfs.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days 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.19% · top 91% of all CVEs (16 Nov 2026)
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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8a3a54aa3e65ed76f8560a387243a7738ae0cb1c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5c7ab4ca66f0880cffc3735555ea719dd5253726
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 53407535d49ec034e476121020b5c878f0d92e18
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e7730acd6a01c5931a3afb83639810ff2fb9cc92
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 77272b7fd0e472086fd626a1fcd11da625822cc2
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c2d4174f492458ecdcdef309243624999612d526
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6351e94076329dab517ea94c115e15c4d8459381
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f82f53e75eff382fc8f56b73279b54f7cf5a5c65
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .