Linux kernel
cpe:2.3:a:linux:linux_kernel:*:*:*:*:*:*:*, +4 more
A vulnerability in the Linux kernel's RDMA/hfi1 component can lead to the use of an uninitialized lock. This issue arises if the probing of hfi1 fails before the sdma_map_lock is initialized. Consequently, the hfi1_free_devdata() function may attempt to use this uninitialized lock. When the locking correctness validator is active, this can trigger an INFO message along with a stack trace indicating a registration issue with a non-static key. The sdma_map_lock is intended for managing sdma_map memory, which is not allocated until after the lock is initialized. To avoid this vulnerability, the code should check if sdma_map is not NULL before attempting to use the lock.
Exploitation of this vulnerability can lead to improper locking behavior, potentially causing synchronization issues in the RDMA/hfi1 component.
Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.