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-93819 Overview
CVE-2026-93819 is a race condition in the Linux kernel's MediaTek PCI controller driver. The flaw occurs when a root bus is stopped and removed without holding the pci_rescan_remove_lock. Concurrent rescan or hotplug operations triggered through sysfs can interleave with the removal path and lead to use-after-free conditions or system crashes. The upstream fix acquires the rescan/remove lock around the root bus teardown to serialize these operations.
Critical Impact
Concurrent sysfs-triggered rescan or hotplug operations can race with MediaTek PCI root bus removal, resulting in use-after-free memory corruption or kernel crashes.
Affected Products
- Linux kernel versions containing the MediaTek PCI host controller driver (pci-mediatek) prior to the fix
- Platforms using MediaTek PCIe root complexes
- Downstream distributions shipping the vulnerable pci-mediatek driver
Discovery Timeline
- 2026-09-24 - CVE-2026-93819 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-93819
Vulnerability Analysis
The MediaTek PCI controller driver tears down a root bus by stopping and removing it during driver unbind or shutdown. The removal path did not hold pci_rescan_remove_lock, which is the lock the kernel uses to serialize bus rescan and remove operations against sysfs-driven activity. Without that lock, a user-space write to a sysfs attribute such as rescan or remove can begin walking or mutating PCI device structures while the driver concurrently frees them.
This is a classic race condition [CWE-362] that enables a use-after-free [CWE-416] on pci_dev or pci_bus structures. Depending on which structures are freed and reused, the result ranges from kernel oops to broader memory corruption affecting system stability.
Root Cause
The root cause is missing synchronization. The MediaTek driver's bus teardown routine invoked pci_stop_root_bus() and pci_remove_root_bus() without acquiring pci_rescan_remove_lock, violating the locking contract that protects these operations from concurrent sysfs rescan and hotplug code paths.
Attack Vector
Triggering the race requires local access and the ability to interact with PCI sysfs attributes, which are typically restricted to privileged users. An actor with sufficient privilege can script repeated writes to PCI rescan, remove, or hotplug sysfs nodes while the MediaTek driver unbinds, increasing the likelihood of hitting the window. Successful exploitation yields a kernel-mode use-after-free that can crash the system.
No public proof-of-concept is referenced in the available data. See the upstream kernel commits for the exact code paths and fix: kernel commit a29812a5, kernel commit a5689394, and kernel commit c57b9717.
Detection Methods for CVE-2026-93819
Indicators of Compromise
- Kernel oops or panic messages referencing pci_stop_root_bus, pci_remove_bus_device, or MediaTek PCI driver symbols
- Use-after-free reports from KASAN implicating pci_dev or pci_bus structures on MediaTek platforms
- Unexpected PCI device disappearance correlated with sysfs writes to /sys/bus/pci/rescan or per-device remove nodes
Detection Strategies
- Audit kernel versions on MediaTek-based systems and compare against the fixed stable commits listed in the references
- Enable KASAN in test environments to surface use-after-free conditions during driver unbind and concurrent sysfs rescan workloads
- Collect and parse dmesg for crash signatures involving the MediaTek PCI host controller and PCI core removal paths
Monitoring Recommendations
- Centralize kernel logs and alert on panics or oops events on MediaTek platforms
- Monitor sysfs writes to PCI rescan, remove, and hotplug attributes through auditd rules
- Track driver bind and unbind events for pci-mediatek and correlate with system stability metrics
How to Mitigate CVE-2026-93819
Immediate Actions Required
- Apply the upstream Linux kernel patches that acquire pci_rescan_remove_lock around MediaTek root bus removal
- Update to a distribution kernel that includes the fix once available from your vendor
- Restrict access to PCI sysfs attributes to trusted administrators only
Patch Information
The fix holds pci_rescan_remove_lock across the stop and remove sequence of the MediaTek PCI root bus. The relevant stable tree commits are a29812a55da8, a568939487dc, and c57b971765f8. Rebuild and reboot into the patched kernel on affected MediaTek platforms.
Workarounds
- Avoid issuing concurrent writes to PCI rescan, remove, or hotplug sysfs nodes while the MediaTek driver may be unbinding
- Limit sysfs PCI write permissions to the root user and remove unnecessary administrative tooling that triggers rescans
- Defer driver unbind operations until all PCI management activity is quiesced
# Verify running kernel and check for the fix commit in your distribution's changelog
uname -r
# Restrict access to PCI rescan and remove attributes
chmod 600 /sys/bus/pci/rescan
find /sys/bus/pci/devices -name remove -exec chmod 600 {} \;
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

