CVE-2026-93822Hinoki check available

System crash via unlocked PCI root bus removal

Published Sep 24, 2026 · Updated Sep 24, 2026

Race condition in the iProc PCIe controller in Linux before 6.12.111 or 6.18.53 allows local users to crash the system. The iproc_pcie_remove() path stops and removes the root bus without holding pci_rescan_remove_lock, allowing concurrent sysfs rescan or hotplug work to use freed objects. Exploitation requires privileged PCI sysfs activity during driver teardown on hardware using the iProc PCIe controller; the bounded consequence is a kernel crash.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Race condition in the iProc PCIe controller in Linux before 6.12.111 or 6.18.53 allows local users to crash the system. The iproc_pcie_remove() path stops and removes the root bus without holding pci_rescan_remove_lock, allowing concurrent sysfs rescan or hotplug work to use freed objects. Exploitation requires privileged PCI sysfs activity during driver teardown on hardware using the iProc PCIe controller; the bounded consequence is a kernel crash.

The record

CVE
CVE-2026-93822
Published
Sep 24, 2026
Updated
Sep 24, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Sep 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <6.12.111
  2. Affected versionversion=0 <6.18.53
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a6a64e150f12ad5391e0a0d60f6a3d119b06ce50
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd2bf1e0d973c93fc1637b90cbb9a5a5f6884bd3
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee06aafc2d760a4ee023e0b2e95ce1ec71bddc6c

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

The Linux Kernel Organization · Linuxversion=0 <6.12.111; version=0 <6.18.53; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a6a64e150f12ad5391e0a0d60f6a3d119b06ce50; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd2bf1e0d973c93fc1637b90cbb9a5a5f6884bd3; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee06aafc2d760a4ee023e0b2e95ce1ec71bddc6c

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started