Linux Kernel PCI Slot Locking Error Handling Vulnerability

A vulnerability in the Linux kernel's PCI handling has been addressed. The issue arose in the 'pci_slot_trylock()' function, where the management of locks for bridge devices was improperly handled. Specifically, a recent commit introduced a change that delegated the locking of bridge devices to a bus-level lock, but failed to correctly manage the unlocking process when the operation did not succeed. This oversight could lead to warnings about unlocking a lock that was never acquired, or incorrectly releasing a lock that belongs to a different thread.

Impact

The vulnerability could cause synchronization issues by improperly managing locks, potentially leading to thread safety problems.

Reproduction

The vulnerability can be reproduced by invoking the 'pci_slot_trylock()' function with a slot that is associated with a bridge device. If the function attempts to lock the corresponding bus and fails, it will not properly unlock the bridge device, creating a mismatch in the locking mechanism.

Remediation

Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.