CVE-2022-49433

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/hfi1: Prevent use of lock before it is initialized<br /> <br /> If there is a failure during probe of hfi1 before the sdma_map_lock is<br /> initialized, the call to hfi1_free_devdata() will attempt to use a lock<br /> that has not been initialized. If the locking correctness validator is on<br /> then an INFO message and stack trace resembling the following may be seen:<br /> <br /> INFO: trying to register non-static key.<br /> The code is fine but needs lockdep annotation, or maybe<br /> you didn&amp;#39;t initialize this object before use?<br /> turning off the locking correctness validator.<br /> Call Trace:<br /> register_lock_class+0x11b/0x880<br /> __lock_acquire+0xf3/0x7930<br /> lock_acquire+0xff/0x2d0<br /> _raw_spin_lock_irq+0x46/0x60<br /> sdma_clean+0x42a/0x660 [hfi1]<br /> hfi1_free_devdata+0x3a7/0x420 [hfi1]<br /> init_one+0x867/0x11a0 [hfi1]<br /> pci_device_probe+0x40e/0x8d0<br /> <br /> The use of sdma_map_lock in sdma_clean() is for freeing the sdma_map<br /> memory, and sdma_map is not allocated/initialized until after<br /> sdma_map_lock has been initialized. This code only needs to be run if<br /> sdma_map is not NULL, and so checking for that condition will avoid trying<br /> to use the lock before it is initialized.