dbcve.org
Linux KernelOperating system · Linux

CVE-2024-26744

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-03
Fix available
A fix is available. Upgrade to 4.19.308 / 5.10.211 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Support specifying the srpt_service_guid parameter Make loading ib_srpt with this parameter set work. The current behavior is that setting that parameter while loading the ib_srpt kernel module triggers the following kernel crash: BUG: kernel NULL pointer dereference, address: 0000000000000000 Call Trace: <TASK> parse_one+0x18c/0x1d0 parse_args+0xe1/0x230 load_module+0x8de/0xa60 init_module_from_file+0x8b/0xd0 idempotent_init_module+0x181/0x240 __x64_sys_finit_module+0x5a/0xb0 do_syscall_64+0x5f/0xe0 entry_SYSCALL_64_after_hwframe+0x6e/0x76

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-476

The code follows a pointer that is null, crashing the process. An attacker who can reliably trigger it turns the crash into a denial of service. The fix is checking for null before use and handling the failure path gracefully.

General guidance for the null pointer dereference class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 3.3, < 4.19.308>= 4.20, < 5.10.211>= 5.11, < 5.15.150>= 5.16, < 6.1.80>= 6.2, < 6.6.19>= 6.7, < 6.7.7= 6.8
Debian LinuxOperating system
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.19.308 / 5.10.211 / 5.15.150 or later
Fixed in 4.19.3085.10.2115.15.150
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel >= 4.19.308, >= 5.10.211, >= 5.15.150, or >= 6.1.80 (depending on which branch is in use). For Debian 10, upgrade to kernel from Debian 11/12 or use upstream kernel >= 6.1.80.

  1. Identify the current running kernel version using `uname -r`
  2. Determine the appropriate upgrade path based on your distribution's kernel versioning
  3. For Debian 10 (Buster), upgrade to a kernel version >= 6.1.80 from Debian backports or consider upgrading to Debian 11/12 for newer kernel support
  4. For enterprise distributions (RHEL, CentOS, etc.), apply vendor-supplied kernel updates that include the fix
  5. After kernel upgrade, reboot the system to load the new kernel
  6. Verify the fix by loading the ib_srpt module with the srpt_service_guid parameter: `modprobe ib_srpt srpt_service_guid=0x...`
  7. Confirm no kernel crash occurs and module loads successfully using `lsmod | grep ib_srpt`
Caveat Kernel upgrades may introduce regression or require adjustment of out-of-tree drivers. Ensure backup and test in non-production environment before deployment.

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26744 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data