LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49429: RDMA/hfi1: Prevent panic when SDMA is disabled

In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent panic when SDMA is disabled If the hfi1 module is loaded with HFI1_CAP_SDMA off, a call to hfi1_write_iter() will dereference a NULL pointer and panic. A typical stack frame is: sdma_select_user_engine [hfi1] hfi1_user_sdma_process_request [hfi1] hfi1_write_iter [hfi1] do_iter_readv_writev do_iter_write vfs_writev do_writev do_syscall_64 The fix is to test for SDMA in hfi1_write_iter() and fail the I/O with EINVAL.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49429 is a Linux kernel flaw in the hfi1 RDMA driver. If the driver is loaded with SDMA disabled, a write path can hit a null pointer and crash the kernel. The business impact is availability loss on specialized systems using this driver, not broad internet-facing compromise based on the provided sources.

Executive priority

Treat as a targeted availability risk. Prioritize affected HPC, storage, or RDMA-dependent systems over general servers. Patch during the next suitable maintenance window unless these systems are business-critical or have observed hfi1-related crashes.

Technical view

The issue is in RDMA/hfi1. With HFI1_CAP_SDMA off, hfi1_write_iter() can call into SDMA handling and dereference a NULL pointer, causing a kernel panic. The upstream fix checks SDMA capability in hfi1_write_iter() and fails the I/O with EINVAL instead of panicking.

Likely exposure

Exposure appears limited to Linux systems using the hfi1 RDMA driver, especially environments with Intel Omni-Path/HFI1 hardware or the hfi1 module loaded, and SDMA disabled. Systems not using this driver are unlikely to be affected based on the provided description.

Exploitation context

The sources do not report active exploitation, and CISA KEV status is false. The described impact is a kernel panic triggered through the hfi1 write path when SDMA is disabled. No remote exploitation path is identified in the provided material.

Researcher notes

The CVE record provides no CVSS, CWE, or exploit evidence. Affected version data is partly commit-oriented and should be reconciled with distribution kernel advisories. The fix behavior is clear: detect missing SDMA capability and return EINVAL rather than dereferencing NULL.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable hfi1 fix.
  • Prioritize clusters or servers using hfi1 RDMA or Omni-Path adapters.
  • If patching is delayed, review vendor guidance for safely disabling unused hfi1 functionality.
  • Avoid ad hoc driver changes unless validated by the OS or kernel vendor.

Validation and detection

  • Inventory Linux systems for loaded or packaged hfi1 kernel modules.
  • Identify hosts with HFI1/Omni-Path hardware or RDMA workloads.
  • Compare running kernel builds against vendor updates containing the referenced commits.
  • Check whether SDMA-disabled hfi1 configurations exist in production.
  • Monitor affected hosts for kernel panic reports referencing hfi1_write_iter or SDMA.
Prepared
Confidence
medium
Sources
10

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-49429 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
9Source 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
LinuxLinux0cb2aa690c7ef14ad1f544288349abb5434bb75d, 0cb2aa690c7ef14ad1f544288349abb5434bb75d, 0cb2aa690c7ef14ad1f544288349abb5434bb75d, 0cb2aa690c7ef14ad1f544288349abb5434bb75d, 0cb2aa690c7ef14ad1f544288349abb5434bb75d, 0cb2aa690c7ef14ad1f544288349abb5434bb75d, 0cb2aa690c7ef14ad1f544288349abb5434bb75d, 0cb2aa690c7ef14ad1f544288349abb5434bb75dunaffected
LinuxLinux4.9, 0, 4.14.283, 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.