CVE-2022-49433
published 2025-02-26CVE-2022-49433: 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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
18.2th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 7724105686e718ac476a6ad3304fea2fbcfcffde < 66090815a24ce14cf51ef5453fc0218fe8a39bc2 | 66090815a24ce14cf51ef5453fc0218fe8a39bc2 |
| linux | linux | >= 7724105686e718ac476a6ad3304fea2fbcfcffde < addb192000d8819c0b1553453994df9bb54c28db | addb192000d8819c0b1553453994df9bb54c28db |
| linux | linux | >= 7724105686e718ac476a6ad3304fea2fbcfcffde < fc0750e659db7b315bf6348902cc8ca3cdd4b8d8 | fc0750e659db7b315bf6348902cc8ca3cdd4b8d8 |
| linux | linux | >= 7724105686e718ac476a6ad3304fea2fbcfcffde < ca55150bff5817af4f857a746ecab9862c23e12a | ca55150bff5817af4f857a746ecab9862c23e12a |
| linux | linux | >= 7724105686e718ac476a6ad3304fea2fbcfcffde < 30eb275e7ed588270ae159cc590a96658e0cfd8f | 30eb275e7ed588270ae159cc590a96658e0cfd8f |
| linux | linux | >= 7724105686e718ac476a6ad3304fea2fbcfcffde < 288d198f50434f29b4a26a9de4394ae2305ad8af | 288d198f50434f29b4a26a9de4394ae2305ad8af |
| linux | linux | >= 7724105686e718ac476a6ad3304fea2fbcfcffde < 05c03dfd09c069c4ffd783b47b2da5dcc9421f2c | 05c03dfd09c069c4ffd783b47b2da5dcc9421f2c |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 4.20 < 5.4.198 | 5.4.198 |
| linux | linux_kernel | >= 4.3 < 4.19.247 | 4.19.247 |
| linux | linux_kernel | >= 5.11 < 5.15.46 | 5.15.46 |
| linux | linux_kernel | >= 5.16 < 5.17.14 | 5.17.14 |
| linux | linux_kernel | >= 5.18 < 5.18.3 | 5.18.3 |
| linux | linux_kernel | >= 5.5 < 5.10.121 | 5.10.121 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-g569-wg4c-8crr: 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 du
ghsa_unreviewed·2025-10-22
CVE-2022-49433 [MEDIUM] CWE-908 GHSA-g569-wg4c-8crr: 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 du
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]
OSV
CVE-2022-49433: 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 duri
osv·2025-02-26·CVSS 5.5
CVE-2022-49433 [MEDIUM] CVE-2022-49433: 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 duri
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] ini
Red Hat
kernel: RDMA/hfi1: Prevent use of lock before it is initialized
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49433 [MEDIUM] kernel: RDMA/hfi1: Prevent use of lock before it is initialized
kernel: RDMA/hfi1: Prevent use of lock before it is initialized
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_
Debian
CVE-2022-49433: linux - In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: ...
vendor_debian·2022·CVSS 5.5
CVE-2022-49433 [MEDIUM] CVE-2022-49433: linux - In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: ...
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] ini
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/05c03dfd09c069c4ffd783b47b2da5dcc9421f2chttps://git.kernel.org/stable/c/288d198f50434f29b4a26a9de4394ae2305ad8afhttps://git.kernel.org/stable/c/30eb275e7ed588270ae159cc590a96658e0cfd8fhttps://git.kernel.org/stable/c/66090815a24ce14cf51ef5453fc0218fe8a39bc2https://git.kernel.org/stable/c/addb192000d8819c0b1553453994df9bb54c28dbhttps://git.kernel.org/stable/c/ca55150bff5817af4f857a746ecab9862c23e12ahttps://git.kernel.org/stable/c/fc0750e659db7b315bf6348902cc8ca3cdd4b8d8
2025-02-26
Published