Security readout for executives and security teams
Plain-English summary
CVE-2024-50095 is a Linux kernel availability flaw in RDMA message handling. Under heavy timed-out work requests, locking contention can cause a CPU soft lockup. The business risk is service disruption on Linux systems that use RDMA paths, not data theft or remote code execution based on the supplied evidence.
Executive priority
Treat this as a targeted availability risk for RDMA-capable Linux infrastructure. Prioritize patching where RDMA supports production storage, clustering, high-performance computing, or industrial systems. It is less urgent for ordinary Linux servers without RDMA exposure.
Technical view
The RDMA/mad timeout handler repeatedly acquired and released a mad_agent_priv lock while processing timed-out work requests. High WR volume could create severe lock contention and soft lockup in rdma-cm connection paths. The fix builds a local list while holding the lock once, then invokes send handlers after releasing it.
Likely exposure
Exposure is most likely on Linux hosts with RDMA, InfiniBand, ib_core, or rdma-cm usage. The CVSS vector is local with low privileges and high availability impact. The bundle lists Linux as affected and includes stable kernel commits plus Debian LTS and Siemens advisories.
Exploitation context
The supplied sources do not show active exploitation, and KEV is false. The vulnerability requires local access with low privileges according to the CVSS vector. Evidence supports denial of service through soft lockup conditions, not confidentiality or integrity compromise.
Researcher notes
The public record describes the root cause and kernel-side fix but does not include a CWE, exploit procedure, or complete downstream product matrix. Researchers should focus validation on affected kernel lineage, RDMA enablement, and whether vendor kernels have backported the stable commits.
Mitigation direction
Upgrade to a kernel containing the stable RDMA/mad fix from the referenced Linux commits.
Apply Debian LTS or vendor advisories where they govern your kernel supply chain.
For Siemens environments, follow SSA-265688 and SSA-355557 product guidance.
Prioritize RDMA-enabled hosts and systems using rdma-cm connection paths.
If no vendor package is available, track vendor guidance before deploying custom kernels.
Validation and detection
Inventory kernels and identify hosts with RDMA, InfiniBand, or ib_core usage.
Compare running kernel versions against vendor packages that include the referenced stable commits.
Review kernel logs for soft lockup reports in ib_mad timeout_sends workqueues.
Confirm remediation through package metadata or vendor advisory mapping, not version strings alone.
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-2024-50095 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.