Service interruption via unbounded UMAD receive queue
Published Jul 30, 2024 · Updated Aug 5, 2026
Resource exhaustion in the Linux kernel's ib_umad interface allows remote attackers to interrupt service via excessive MAD traffic. The receive path in drivers/infiniband/core/user_mad.c appends received MAD packets to a list without limiting its size when userspace drains packets more slowly than they arrive. Exposure requires an active userspace MAD consumer and incoming management traffic; sustained queue growth can exhaust memory and interrupt the host.
Summary
What happened
Resource exhaustion in the Linux kernel's ib_umad interface allows remote attackers to interrupt service via excessive MAD traffic. The receive path in drivers/infiniband/core/user_mad.c appends received MAD packets to a list without limiting its size when userspace drains packets more slowly than they arrive. Exposure requires an active userspace MAD consumer and incoming management traffic; sustained queue growth can exhaust memory and interrupt the host.
The record
- CVE
- CVE-2024-42145
- Published
- Jul 30, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-770, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1288cf1cceb0e6df276e182f5412370fb4169bcb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <62349fbf86b5e13b02721bdadf98c29afd1e7b5f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63d202d948bb6d3a28cd8e8b96b160fa53e18baa
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a6627fba793cc75b7365d9504a0095fb2902dda4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b4913702419d064ec4c4bbf7270643c95cc89a1b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b8c5f635997f49c625178d1a0cb32a80ed33abe6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ca0b44e20a6f3032224599f02e7c8fb49525c894
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d73cb8862e4d6760ccc94d3b57b9ef6271400607
- Affected versionversion=2.6.12
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.
Weakness, pattern, technique
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