CVE-2022-49433 Details
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent use of lock before it is initialized If there is a failure during probe of hfi1 before the sdma_map_lock is initialized, the call to hfi1_free_devdata() will attempt to use a lock that has not been initialized. If the locking correctness validator is on then an INFO message and stack trace resembling the following may be seen: INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validator. Call Trace: register_lock_class+0x11b/0x880 __lock_acquire+0xf3/0x7930 lock_acquire+0xff/0x2d0 _raw_spin_lock_irq+0x46/0x60 sdma_clean+0x42a/0x660 [hfi1] hfi1_free_devdata+0x3a7/0x420 [hfi1] init_one+0x867/0x11a0 [hfi1] pci_device_probe+0x40e/0x8d0 The use of sdma_map_lock in sdma_clean() is for freeing the sdma_map memory, and sdma_map is not allocated/initialized until after sdma_map_lock has been initialized. This code only needs to be run if sdma_map is not NULL, and so checking for that condition will avoid trying to use the lock before it is initialized.
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.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/05c03dfd09c069c4ffd783b47b2da5dcc9421f2c | kernel.org | Patch |
| https://git.kernel.org/stable/c/288d198f50434f29b4a26a9de4394ae2305ad8af | kernel.org | Patch |
| https://git.kernel.org/stable/c/30eb275e7ed588270ae159cc590a96658e0cfd8f | kernel.org | Patch |
| https://git.kernel.org/stable/c/66090815a24ce14cf51ef5453fc0218fe8a39bc2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/addb192000d8819c0b1553453994df9bb54c28db | kernel.org | Patch |
| https://git.kernel.org/stable/c/ca55150bff5817af4f857a746ecab9862c23e12a | kernel.org | Patch |
| https://git.kernel.org/stable/c/fc0750e659db7b315bf6348902cc8ca3cdd4b8d8 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-908 | Use of Uninitialized Resource | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.3, < 4.19.247 >= 4.20, < 5.4.198 >= 5.5, < 5.10.121 >= 5.11, < 5.15.46 >= 5.16, < 5.17.14 >= 5.18, < 5.18.3 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 22, 2025 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |