CVE-2026-93206

PCI/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.

Key facts

Published
24 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.189% likely to be exploited in the next 30 days, higher than 8.632% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 8a3a54aa3e65ed76f8560a387243a7738ae0cb1c (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 5c7ab4ca66f0880cffc3735555ea719dd5253726 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 53407535d49ec034e476121020b5c878f0d92e18 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding e7730acd6a01c5931a3afb83639810ff2fb9cc92 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 77272b7fd0e472086fd626a1fcd11da625822cc2 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding c2d4174f492458ecdcdef309243624999612d526 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding 6351e94076329dab517ea94c115e15c4d8459381 (affected)
  • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to but excluding f82f53e75eff382fc8f56b73279b54f7cf5a5c65 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.12 (affected)
  • 0 up to but excluding 2.6.12 (unaffected)
  • 5.10.270 up to and including 5.10.* (unaffected)
  • 5.15.221 up to and including 5.15.* (unaffected)
  • 6.1.188 up to and including 6.1.* (unaffected)
  • 6.6.157 up to and including 6.6.* (unaffected)
  • 6.12.109 up to and including 6.12.* (unaffected)
  • 6.18.50 up to and including 6.18.* (unaffected)
  • 7.2.4 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References