CVE-2022-49433
RDMA/hfi1: Prevent use of lock before it is initialized
- Published
- Updated
- Reserved
- Assigned by
- Linux
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.27% · top 81% of all CVEs (6 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected 7724105686e718ac476a6ad3304fea2fbcfcffde – < 66090815a24ce14cf51ef5453fc0218fe8a39bc2
- affected 7724105686e718ac476a6ad3304fea2fbcfcffde – < addb192000d8819c0b1553453994df9bb54c28db
- affected 7724105686e718ac476a6ad3304fea2fbcfcffde – < fc0750e659db7b315bf6348902cc8ca3cdd4b8d8
- affected 7724105686e718ac476a6ad3304fea2fbcfcffde – < ca55150bff5817af4f857a746ecab9862c23e12a
- affected 7724105686e718ac476a6ad3304fea2fbcfcffde – < 30eb275e7ed588270ae159cc590a96658e0cfd8f
- affected 7724105686e718ac476a6ad3304fea2fbcfcffde – < 288d198f50434f29b4a26a9de4394ae2305ad8af
- affected 7724105686e718ac476a6ad3304fea2fbcfcffde – < 05c03dfd09c069c4ffd783b47b2da5dcc9421f2c
- affected 4.3
- unaffected < 4.3
- unaffected 4.19.247 – ≤ 4.19.*
- unaffected 5.4.198 – ≤ 5.4.*
- unaffected 5.10.121 – ≤ 5.10.*
- unaffected 5.15.46 – ≤ 5.15.*
- unaffected 5.17.14 – ≤ 5.17.*
- unaffected 5.18.3 – ≤ 5.18.*
- unaffected 5.19 – ≤ *
References (7)
- https://git.kernel.org/stable/c/66090815a24ce14cf51ef5453fc0218fe8a39bc2 (opens in a new tab)
- https://git.kernel.org/stable/c/addb192000d8819c0b1553453994df9bb54c28db (opens in a new tab)
- https://git.kernel.org/stable/c/fc0750e659db7b315bf6348902cc8ca3cdd4b8d8 (opens in a new tab)
- https://git.kernel.org/stable/c/ca55150bff5817af4f857a746ecab9862c23e12a (opens in a new tab)
- https://git.kernel.org/stable/c/30eb275e7ed588270ae159cc590a96658e0cfd8f (opens in a new tab)
- https://git.kernel.org/stable/c/288d198f50434f29b4a26a9de4394ae2305ad8af (opens in a new tab)
- https://git.kernel.org/stable/c/05c03dfd09c069c4ffd783b47b2da5dcc9421f2c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-49433)Record last updated .