Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a reference-count leak in the Hisilicon hns RoCE RDMA mmap path. In practical terms, affected systems may fail to release an internal kernel reference after a user mapping operation. The likely business risk is local resource exhaustion or instability on systems using this RDMA hardware and driver.
Executive priority
Treat as a targeted infrastructure maintenance issue, not a broad emergency. Prioritize patching specialized RDMA-capable Linux servers, especially in data center, HPC, storage, or low-latency environments. Business urgency increases if untrusted local users or workloads can access RDMA device interfaces.
Technical view
The bug is in RDMA/hns hns_roce_mmap. rdma_user_mmap_entry_get_pgoff() increments a reference, but the vulnerable path failed to call rdma_user_mmap_entry_put() to release it. The kernel stable fixes add the missing put operation. No CVSS, CWE, or detailed impact rating is provided in the source bundle.
Likely exposure
Exposure appears limited to Linux systems using the hns RoCE RDMA driver, typically with Hisilicon RDMA hardware enabled. General Linux servers without this driver or hardware are less likely to be exposed. Version metadata is incomplete and should be verified against vendor kernels.
Exploitation context
The provided sources do not show active exploitation, public weaponization, or CISA KEV listing. The issue appears local and driver-specific because it involves a kernel mmap path for RDMA user mappings. Practical exploitability depends on access to the RDMA device interface and affected kernel code.
Researcher notes
The public record lacks CVSS, CWE, and full affected-version ranges. The core fix is narrow: add rdma_user_mmap_entry_put() after rdma_user_mmap_entry_get_pgoff(). Further assessment should focus on reachable mmap paths, required device permissions, and whether repeated mappings can cause measurable kernel resource exhaustion.
Mitigation direction
- Update to a kernel or distribution package containing the referenced stable fixes.
- Check your Linux vendor advisory for exact affected and fixed package versions.
- Prioritize systems with hns RoCE RDMA hardware or the hns_roce driver enabled.
- If immediate patching is unavailable, review vendor guidance on disabling unused RDMA functionality.
Validation and detection
- Inventory Linux systems using Hisilicon hns RoCE RDMA hardware.
- Check whether the hns_roce driver is present or enabled.
- Compare running kernel packages against vendor fixed versions or stable commits.
- Confirm remediation by verifying the vendor kernel includes the missing reference release fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2022-50775 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.