Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-93822 Overview
CVE-2026-93822 is a race condition vulnerability in the Linux kernel's Broadcom iProc PCI host controller driver. The flaw occurs because root bus stop-and-remove operations execute without holding the pci_rescan_remove_lock. Concurrent rescan or hotplug operations triggered through sysfs can race with the removal path. This may lead to use-after-free conditions or system crashes on affected systems.
The issue has been resolved upstream through commits that acquire pci_rescan_remove_lock for the duration of root bus teardown in the iProc PCI driver.
Critical Impact
Concurrent sysfs-triggered PCI rescan or hotplug operations can race with root bus removal, producing use-after-free memory corruption or kernel crashes on systems using the Broadcom iProc PCI host controller.
Affected Products
- Linux kernel versions containing the vulnerable Broadcom iProc PCI host controller driver (drivers/pci/controller/pcie-iproc)
- Systems-on-chip based on Broadcom iProc platforms that enable the PCIe host controller
- Stable Linux kernel branches prior to the backported fix commits
Discovery Timeline
- 2026-09-24 - CVE-2026-93822 published to the National Vulnerability Database
- 2026-09-25 - Last updated in the NVD database
Technical Details for CVE-2026-93822
Vulnerability Analysis
The Linux kernel exposes PCI rescan and device removal operations through sysfs interfaces such as /sys/bus/pci/rescan and per-device remove attributes. The kernel serializes these operations with the global pci_rescan_remove_lock mutex to prevent concurrent modification of the PCI device tree.
The Broadcom iProc PCI host controller driver stopped and removed the root bus during teardown without acquiring this lock. A privileged administrator or automated management agent could trigger a rescan or hotplug event through sysfs while the driver was tearing down the same root bus. The two paths then manipulated overlapping PCI device structures without serialization.
The outcome is a classic time-of-check to time-of-use condition [CWE-362] against reference-counted kernel objects. Dangling pointers to freed pci_dev or pci_bus structures can be dereferenced after one path releases memory the other still holds.
Root Cause
The iProc driver's root bus removal routine omitted the pci_rescan_remove_lock acquisition that other PCI controller drivers hold during equivalent operations. Without this lock, the removal path and the sysfs-driven rescan path can execute concurrently against the same device tree.
Attack Vector
Exploitation requires local access with permission to write PCI sysfs attributes, typically root or an equivalent capability. An attacker triggers a sysfs rescan or hotplug operation while the iProc driver is unbinding or shutting down. The resulting use-after-free can cause a kernel crash (denial of service) or, under favorable conditions, memory corruption in kernel address space.
See the upstream fix in the kernel git commit and its stable backports for the exact locking change.
Detection Methods for CVE-2026-93822
Indicators of Compromise
- Unexpected kernel oops or panic messages referencing pci_stop_root_bus, pci_remove_root_bus, or iProc driver symbols
- Kernel log entries showing use-after-free reports from KASAN during PCI rescan or hotplug activity
- System crashes correlated in time with writes to /sys/bus/pci/rescan or /sys/bus/pci/devices/*/remove
Detection Strategies
- Review kernel version strings on Broadcom iProc platforms and compare against the fixed stable releases referenced in the upstream commits
- Audit root-owned processes and management agents that interact with PCI sysfs attributes for unexpected rescan or remove activity
- Enable kernel address sanitizer (KASAN) or lockdep in test environments to surface the race during PCI stress testing
Monitoring Recommendations
- Forward kernel ring buffer logs (dmesg, journalctl -k) to a centralized logging platform and alert on BUG:, WARNING:, or KASAN events tied to PCI subsystems
- Monitor file access to PCI sysfs paths using auditd rules targeting /sys/bus/pci/rescan and per-device remove nodes
- Track unplanned reboots on Broadcom iProc-based appliances and correlate them with PCI driver activity
How to Mitigate CVE-2026-93822
Immediate Actions Required
- Upgrade affected Linux systems to a stable kernel release that includes the iProc PCI locking fix referenced in the upstream commits
- Restrict write access to PCI sysfs attributes to trusted administrators and limit automated agents that trigger rescan or hotplug operations
- Inventory Broadcom iProc-based hardware in the environment and prioritize patching for devices exposed to multi-tenant or untrusted administrative workflows
Patch Information
The fix is available in the mainline Linux kernel and backported to stable branches. Review the upstream commits a6a64e150f12, bd2bf1e0d973, and ee06aafc2d76 to confirm the patched versions applicable to your kernel branch. Apply vendor-provided kernel updates from your Linux distribution once available.
Workarounds
- Avoid concurrent PCI rescan or hotplug operations on Broadcom iProc platforms until the patched kernel is installed
- Remove or restrict permissions on sysfs PCI control files for non-essential users and services
- Disable runtime PCI hotplug management agents on affected hosts where operationally feasible
# Restrict access to PCI rescan sysfs interface until patched kernel is deployed
chmod 600 /sys/bus/pci/rescan
# Identify running kernel version to compare against patched stable releases
uname -r
# Audit writes to PCI control sysfs attributes
auditctl -w /sys/bus/pci/rescan -p w -k pci_rescan
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

