System hang via RDMA timeout lock contention
Published Nov 5, 2024 · Updated Aug 5, 2026
Improper locking in Linux kernel RDMA MAD handling allows remote attackers to hang an RDMA node by flooding connection requests. The timeout_sends handler repeatedly releases and reacquires mad_agent_priv for every expired work request, causing severe contention when many requests expire together. Reachability requires an RDMA CM listener over an exposed IB or RoCE interface; the bounded consequence is a CPU soft lockup and service interruption.
Summary
What happened
Improper locking in Linux kernel RDMA MAD handling allows remote attackers to hang an RDMA node by flooding connection requests. The timeout_sends handler repeatedly releases and reacquires mad_agent_priv for every expired work request, causing severe contention when many requests expire together. Reachability requires an RDMA CM listener over an exposed IB or RoCE interface; the bounded consequence is a CPU soft lockup and service interruption.
The record
- CVE
- CVE-2024-50095
- Published
- Nov 5, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- CWE-667, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <V3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo