Unknown

CVE-2026-93206 — PCI/proc: Use file_ns_capable() when checking config space read access

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.

Published Sep 24, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.19%

ahead of 8% of scored CVEs · Oct 16, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 8a3a54aa3e65ed76f8560a387243a7738ae0cb1c≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 5c7ab4ca66f0880cffc3735555ea719dd5253726≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 53407535d49ec034e476121020b5c878f0d92e18≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e7730acd6a01c5931a3afb83639810ff2fb9cc92≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 77272b7fd0e472086fd626a1fcd11da625822cc2≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < c2d4174f492458ecdcdef309243624999612d526≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 6351e94076329dab517ea94c115e15c4d8459381≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f82f53e75eff382fc8f56b73279b54f7cf5a5c65 and 1 more version 2.6.12	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.19%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 24, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/6351e94076329dab517ea94c115e15c4d8459381
NIST National Vulnerability Database
git.kernel.org/stable/c/e7730acd6a01c5931a3afb83639810ff2fb9cc92
NIST National Vulnerability Database
git.kernel.org/stable/c/f82f53e75eff382fc8f56b73279b54f7cf5a5c65
NIST National Vulnerability Database
git.kernel.org/stable/c/77272b7fd0e472086fd626a1fcd11da625822cc2
NIST National Vulnerability Database
git.kernel.org/stable/c/5c7ab4ca66f0880cffc3735555ea719dd5253726
NIST National Vulnerability Database
git.kernel.org/stable/c/8a3a54aa3e65ed76f8560a387243a7738ae0cb1c
NIST National Vulnerability Database
git.kernel.org/stable/c/c2d4174f492458ecdcdef309243624999612d526
NIST National Vulnerability Database
git.kernel.org/stable/c/53407535d49ec034e476121020b5c878f0d92e18
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 5h
Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 5h
Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 5h
Unknown CVE-2026-98860 HID: bpf: cast size to ssize_t when checking hid_bpf_hw_request 5h
Unknown CVE-2026-98865 sched_ext: Don't run ops.dequeue() with a DSQ lock held 5h
Unknown CVE-2026-98864 sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task 5h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-93206 is "PCI/proc: Use file_ns_capable() when checking config space read access", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.