Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-42145: IB/core: Implement a limit on UMAD receive List

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.87% (FIRST EPSS); higher than 59% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1288cf1cceb0e6df276e182f5412370fb4169bcb, 62349fbf86b5e13b02721bdadf98c29afd1e7b5f, 63d202d948bb6d3a28cd8e8b96b160fa53e18baa.
  • Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1288cf1cceb0e6df276e182f5412370fb4169bcb, 62349fbf86b5e13b02721bdadf98c29afd1e7b5f, 63d202d948bb6d3a28cd8e8b96b160fa53e18baa or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 30, 2024
Updated
Aug 5, 2026
EPSS
0.8% · 59th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.5
2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-42145

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.19.318
  • linux linux kernel4.20 and later · before 5.4.280
  • linux linux kernel5.5 and later · before 5.10.222
  • linux linux kernel5.11 and later · before 5.15.163
  • linux linux kernel5.16 and later · before 6.1.98
  • linux linux kernel6.2 and later · before 6.6.39
  • linux linux kernel6.7 and later · before 6.9.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1288cf1cceb0e6df276e182f5412370fb4169bcbaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b4913702419d064ec4c4bbf7270643c95cc89a1baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 62349fbf86b5e13b02721bdadf98c29afd1e7b5faffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d73cb8862e4d6760ccc94d3b57b9ef6271400607affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 63d202d948bb6d3a28cd8e8b96b160fa53e18baaaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b8c5f635997f49c625178d1a0cb32a80ed33abe6affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a6627fba793cc75b7365d9504a0095fb2902dda4affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ca0b44e20a6f3032224599f02e7c8fb49525c894affected · git
    • before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.98-16.1.98-1
Debian:13linuxbefore 6.9.9-16.9.9-1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-defaultbefore 3.0.101-108.159.13.0.101-108.159.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-defaultbefore 3.0.101-108.168.13.0.101-108.168.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-ec2before 3.0.101-108.159.13.0.101-108.159.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-ec2before 3.0.101-108.168.13.0.101-108.168.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-sourcebefore 3.0.101-108.168.13.0.101-108.168.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-sourcebefore 3.0.101-108.159.13.0.101-108.159.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-symsbefore 3.0.101-108.159.13.0.101-108.159.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-symsbefore 3.0.101-108.168.13.0.101-108.168.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-tracebefore 3.0.101-108.159.13.0.101-108.159.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-tracebefore 3.0.101-108.168.13.0.101-108.168.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-xenbefore 3.0.101-108.168.13.0.101-108.168.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-xenbefore 3.0.101-108.159.13.0.101-108.159.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-42142Jul 30, 2024 · net/mlx5: E-switch, Create ingress ACL when needed
    22Monitor
  • ← EarlierCVE-2024-42144Jul 30, 2024 · thermal/drivers/mediatek/lvts_thermal: Check NULL ptr on lvts_data
    22Monitor
  • Later →CVE-2024-42146Jul 30, 2024 · drm/xe: Add outer runtime_pm protection to xe_live_ktest@xe_dma_buf
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1288cf1cceb0e6df276e182f5412370fb4169bcbVendor (CNA)
Linux Linux62349fbf86b5e13b02721bdadf98c29afd1e7b5fVendor (CNA)
Linux Linux63d202d948bb6d3a28cd8e8b96b160fa53e18baaVendor (CNA)
Linux Linuxa6627fba793cc75b7365d9504a0095fb2902dda4Vendor (CNA)
Linux Linuxb4913702419d064ec4c4bbf7270643c95cc89a1bVendor (CNA)
Linux Linuxb8c5f635997f49c625178d1a0cb32a80ed33abe6Vendor (CNA)
Linux Linuxca0b44e20a6f3032224599f02e7c8fb49525c894Vendor (CNA)
Linux Linuxd73cb8862e4d6760ccc94d3b57b9ef6271400607Vendor (CNA)
debian:linux6.1.98-1 · Debian:12Package registry (OSV)
suse:kernel-default3.0.101-108.159.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-ec23.0.101-108.159.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-source3.0.101-108.159.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-syms3.0.101-108.159.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-trace3.0.101-108.159.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-xen3.0.101-108.159.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2021-47137127 days apartnet: lantiq: fix memory corruption in RX ring
    39Monitor
  • CVE-2024-3596971 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr
    35Monitor
  • CVE-2024-3402736 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock
    31Monitor
  • CVE-2021-4755167 days apartdrm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
    31Monitor
  • CVE-2021-47130137 days apartnvmet: fix freeing unallocated p2pmem
    30Monitor
  • CVE-2024-26894104 days apartACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()
    24Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records