CVE-2024-42145: IB/core: Implement a limit on UMAD receive List
In the Linux kernel, the following vulnerability has been resolved:
IB/core: Implement a limit on UMAD receive List
The existing behavior of ib_umad, which maintains received MAD
packets in an unbounded list, poses a risk of uncontrolled growth.
As user-space applications extract packets from this list, the rate
of extraction may not match the rate of incoming packets, leading
to potential list overflow.
To address this, we introduce a limit to the size of the list. After
considering typical scenarios, such as OpenSM processing, which can
handle approximately 100k packets per second, and the 1-second retry
timeout for most packets, we set the list size limit to 200k. Packets
received beyond this limit are dropped, assuming they are likely timed
out by the time they are handled by user-space.
Notably, packets queued on the receive list due to reasons like
timed-out sends are preserved even when the list is full.
Security readout for executives and security teams
Plain-English summary
A Linux kernel InfiniBand/RDMA component could keep incoming management packets in an unlimited queue. If packets arrive faster than user-space can read them, memory/list growth can become excessive. The upstream fix caps the queue and drops excess packets. Business risk is mainly service instability on RDMA/InfiniBand systems, not broad internet-facing compromise.
Executive priority
Treat as a targeted infrastructure stability issue. Patch RDMA and InfiniBand systems during normal security maintenance, faster for clustered compute, storage, or trading environments where RDMA availability matters. No provided evidence supports emergency enterprise-wide action.
Technical view
The issue is in ib_umad/IB core receive handling for MAD packets. Before the fix, received MAD packets accumulated in an unbounded list. The kernel fix sets a 200,000-packet receive-list limit, drops packets beyond that limit, and preserves queued packets tied to timed-out sends.
Likely exposure
Exposure is most likely on Linux hosts using InfiniBand or RDMA management paths, including environments running user-space MAD consumers such as OpenSM. Systems without the relevant hardware, drivers, or ib_umad usage are less likely to be exposed, but version and configuration should be verified locally.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. The described impact requires sustained incoming MAD packet pressure that exceeds user-space processing. Public sources provided do not establish remote reachability, privilege requirements, or a complete attack scenario.
Researcher notes
Key missing evidence includes CVSS, CWE, exploitability details, and vendor-specific fixed versions beyond referenced kernel commits. Validation should focus on reachable ib_umad paths, user-space MAD consumers, and whether deployed kernels include the receive-list limit.
Mitigation direction
Update to a vendor or distribution kernel containing the referenced stable fixes.
Prioritize RDMA and InfiniBand hosts before general-purpose Linux systems.
Check Debian or other distribution advisories for fixed package versions.
Monitor kernel and RDMA subsystem guidance for configuration-specific mitigations.
Validation and detection
Inventory Linux systems with InfiniBand, RDMA, or ib_umad enabled.
Compare running kernel builds against vendor advisories and referenced stable commits.
Review RDMA management services, including OpenSM, on exposed cluster nodes.
Check operational telemetry for unusual MAD traffic or kernel memory pressure.
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-42145 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.