dbcve.org
Linux KernelOperating system · Linux

CVE-2024-49850

MEDIUM · 5.5 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to 6.1.113 / 6.6.54 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: bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos In case of malformed relocation record of kind BPF_CORE_TYPE_ID_LOCAL referencing a non-existing BTF type, function bpf_core_calc_relo_insn would cause a null pointer deference. Fix this by adding a proper check upper in call stack, as malformed relocation records could be passed from user space. Simplest reproducer is a program: r0 = 0 exit With a single relocation record: .insn_off = 0, /* patch first instruction */ .type_id = 100500, /* this type id does not exist */ .access_str_off = 6, /* offset of string "0" */ .kind = BPF_CORE_TYPE_ID_LOCAL, See the link for original reproducer or next commit for a test case.

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:>= 5.17, < 6.1.113>= 6.2, < 6.6.54>= 6.7, < 6.10.13>= 6.11, < 6.11.2

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 6.1.113 / 6.6.54 / 6.10.13 or later
Fixed in 6.1.1136.6.546.10.13
Vendor patch git.kernel.org →
Recommended fix High confidence

Kernel 6.1.113 (for 5.17+ kernels), 6.6.54 (for 6.2+ kernels), 6.10.13 (for 6.7+ kernels), or 6.11.2 (for 6.11+ kernels) depending on your current branch

  1. 1. Identify the current running kernel version using 'uname -r' or 'cat /proc/version'
  2. 2. Determine which affected version range your kernel falls into based on the affected versions list
  3. 3. For systems running kernel >= 5.17 to < 6.1.113: upgrade to kernel version 6.1.113 or later
  4. 4. For systems running kernel >= 6.2 to < 6.6.54: upgrade to kernel version 6.6.54 or later
  5. 5. For systems running kernel >= 6.7 to < 6.10.13: upgrade to kernel version 6.10.13 or later
  6. 6. For systems running kernel >= 6.11 to < 6.11.2: upgrade to kernel version 6.11.2 or later
  7. 7. Apply the vendor patch from commit 2288b54b96dcb55bedebcef3572bb8821fc5e708 if upgrading is not feasible
  8. 8. Reboot the system to load the patched kernel
Caveat Kernel upgrades may require rebuilding out-of-tree kernel modules or drivers; ensure compatibility with dependent software before upgrading

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-49850 — 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-49850 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