LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49433: 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_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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the RDMA hfi1 driver during device probing failure. A cleanup path can try to use a lock before it has been initialized, producing lock validation warnings and stack traces. The source does not provide CVSS, impact severity, or evidence of active exploitation.

Executive priority

Treat this as a targeted kernel hygiene issue, not an emergency based on current evidence. Prioritize patching where hfi1 RDMA is used, and handle other systems through normal kernel maintenance unless vendor advisories raise severity.

Technical view

In RDMA/hfi1, hfi1_free_devdata() can call sdma_clean() after an early probe failure. sdma_clean() may take sdma_map_lock before initialization. The fix conditionally runs the cleanup logic only when sdma_map is non-NULL, matching the allocation and initialization sequence.

Likely exposure

Exposure appears limited to Linux systems with the hfi1 RDMA driver present and relevant affected kernel versions. The bundle lists Linux as affected, but gives incomplete version semantics. Confirm exposure against your distribution kernel package and whether hfi1 hardware or driver loading is in use.

Exploitation context

The bundle does not report active exploitation, and KEV is false. The described symptom is a kernel lock correctness validator warning during a failed hfi1 probe path. No public exploit status, remote attack path, privilege requirement, or business impact rating is provided.

Researcher notes

Evidence is narrow and kernel-specific. The vulnerable path depends on hfi1 probe failure before sdma_map_lock initialization. The source explains the guard condition but does not provide CVSS, CWE, exploitability assessment, or complete affected-version ranges.

Mitigation direction

  • Check your Linux distribution advisory for CVE-2022-49433 guidance.
  • Update to a kernel containing the referenced stable hfi1 fixes.
  • Prioritize systems that load or depend on the hfi1 RDMA driver.
  • If patching is delayed, review vendor-supported options to disable unused hfi1 functionality.

Validation and detection

  • Inventory kernel versions across Linux systems.
  • Check whether the hfi1 module is present, loaded, or required.
  • Compare deployed kernels with vendor fixed package versions.
  • Review kernel logs for hfi1 probe failures or lock validation warnings.
  • Track remediation through standard kernel update verification.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49433 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7724105686e718ac476a6ad3304fea2fbcfcffde, 7724105686e718ac476a6ad3304fea2fbcfcffde, 7724105686e718ac476a6ad3304fea2fbcfcffde, 7724105686e718ac476a6ad3304fea2fbcfcffde, 7724105686e718ac476a6ad3304fea2fbcfcffde, 7724105686e718ac476a6ad3304fea2fbcfcffde, 7724105686e718ac476a6ad3304fea2fbcfcffdeunaffected
LinuxLinux4.3, 0, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.