Skip to main content

Linux EUVDEUVD-2026-85935

| CVE-2026-93206
2026-09-24 Linux GHSA-fjc2-7frc-hj2c
View
Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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.

Affected VersionsENISA

Linux patch: 6.18.50
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e7730acd6a01c5931a3afb83639810ff2fb9cc92
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c2d4174f492458ecdcdef309243624999612d526
Linux 0 <6.18.50
Linux patch: 5.10.270
Linux 0 <5.15.221
Linux 0 <6.1.188
Linux patch: 7.2.4
Linux patch: 6.1.188
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <77272b7fd0e472086fd626a1fcd11da625822cc2
Linux patch: 6.12.109
Linux patch: 5.15.221
Linux 0 <7.2.4
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8a3a54aa3e65ed76f8560a387243a7738ae0cb1c
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5c7ab4ca66f0880cffc3735555ea719dd5253726
Linux patch: 7.3-rc1
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f82f53e75eff382fc8f56b73279b54f7cf5a5c65
Linux 0 <6.6.157
Linux 0 <6.12.109
Linux 0 <5.10.270
Linux patch: 6.6.157
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6351e94076329dab517ea94c115e15c4d8459381
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <53407535d49ec034e476121020b5c878f0d92e18

Affected Packages

euvd linux fix: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Sep 24, 2026 - 16:02 EUVD
CVE Published
Sep 24, 2026 - 15:10 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Data Quality
1 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy