dbcve.org
Linux KernelOperating system · Linux

CVE-2024-50299

MEDIUM · 5.5 CVSS v3.1 Published 2024-11-19
Fix available
A fix is available. Upgrade to 4.19.324 / 5.4.286 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: sctp: properly validate chunk size in sctp_sf_ootb() A size validation fix similar to that in Commit 50619dbf8db7 ("sctp: add size validation when walking chunks") is also required in sctp_sf_ootb() to address a crash reported by syzbot: BUG: KMSAN: uninit-value in sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712 sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712 sctp_do_sm+0x181/0x93d0 net/sctp/sm_sideeffect.c:1166 sctp_endpoint_bh_rcv+0xc38/0xf90 net/sctp/endpointola.c:407 sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88 sctp_rcv+0x3831/0x3b20 net/sctp/input.c:243 sctp4_rcv+0x42/0x50 net/sctp/protocol.c:1159 ip_protocol_deliver_rcu+0xb51/0x13d0 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x336/0x500 net/ipv4/ip_input.c:233

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-908

Memory or a resource is used before it has been initialised, so its contents are whatever happened to be there — sometimes leaking earlier data, sometimes values an attacker can influence. Behaviour becomes unpredictable and occasionally exploitable. Remediation is initialising every resource before use and ensuring initialisation happens on all code paths.

General guidance for the use of uninitialized resource 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:>= 2.6.12, < 4.19.324>= 4.20, < 5.4.286>= 5.5, < 5.10.230>= 5.11, < 5.15.172>= 5.16, < 6.1.117>= 6.2, < 6.6.61>= 6.7, < 6.11.8= 6.12

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.324 / 5.4.286 / 5.10.230 or later
Fixed in 4.19.3245.4.2865.10.230
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 4.19.324 or later (for 4.19.x), 5.4.286 or later (for 5.4.x), 5.10.230 or later (for 5.10.x), or 5.15.172 or later (for 5.15.x)

  1. 1. Identify the current kernel version using `uname -r` or `cat /proc/version`
  2. 2. Determine which branch of the affected version range your kernel falls into (4.19.x, 5.4.x, 5.10.x, or 5.15.x)
  3. 3. For RHEL/CentOS users: Update the kernel package via `yum update kernel` or `dnf update kernel` to a version meeting or exceeding 4.19.324, 5.4.286, 5.10.230, or 5.15.172 as applicable
  4. 4. For Debian/Ubuntu users: Run `apt-get update && apt-get install linux-image-<version>` to install a fixed kernel version
  5. 5. For other distributions: Obtain a kernel from your distribution's security repository that includes the fix commit 0ead60804b64f5bd6999eec88e503c6a1a242d41
  6. 6. Reboot the system to load the updated kernel
  7. 7. Verify the fix is applied by checking `uname -r` matches the expected patched version and confirming the system runs without SCTP-related crashes
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with third-party kernel modules; ensure custom drivers/modules are compatible with the new kernel version

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 $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50299 — 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-50299 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