CVE-2024-50299: sctp: properly validate chunk size in sctp_sf_ootb()
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
Security readout for executives and security teams
Plain-English summary
CVE-2024-50299 is a Linux kernel SCTP bug that can crash a system by mishandling an undersized SCTP chunk. The documented impact is availability loss, not data theft or privilege escalation. It matters most for systems where SCTP is enabled and untrusted local users can reach vulnerable kernel networking code.
Executive priority
Treat this as a planned availability-risk patch, not an emergency breach-response item. Prioritize multi-user servers, container hosts, and Linux-based appliances where a kernel crash would affect critical services.
Technical view
The flaw is missing chunk-size validation in sctp_sf_ootb(), similar to an earlier SCTP chunk-walking validation fix. syzbot reported a KMSAN uninitialized-value crash in the SCTP receive path. CVSS 3.1 is 5.5 with local attack vector, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is most plausible on Linux systems running affected kernel builds with SCTP support enabled. The CVE lists Linux kernel versions from 2.6.12 through several stable lines before their fixed releases. Distribution and appliance kernels may have backported fixes, so exact exposure requires vendor package validation.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The evidence is a syzbot-reported kernel crash and upstream stable fixes. The CVSS vector indicates local, low-privilege exploitation conditions, with availability impact only.
Researcher notes
Evidence supports a kernel availability flaw in SCTP chunk parsing. The source bundle does not provide exploit details, proof of active exploitation, or a universal mitigation beyond applying upstream or vendor fixes. Affected-version data should be reconciled with downstream backports.
Mitigation direction
Upgrade to a kernel or vendor package containing the listed upstream stable fixes.
Check Debian LTS or other distribution advisories for backported fixed kernel packages.
For appliances, follow the relevant vendor advisory rather than assuming upstream version numbers apply.
Reduce SCTP exposure where operationally unnecessary, following vendor-supported configuration guidance.
Validation and detection
Inventory Linux kernels and map them to vendor fixed package advisories.
Confirm whether SCTP support is present and enabled on exposed systems.
Verify the relevant upstream stable commit or distro backport is included.
Prioritize systems where untrusted local users or workloads can access SCTP paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-908: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.