sctp: set sk_state back to CLOSED if autobind fails in sctp_listen_start
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux 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 Linux
2.6.30
- KernelLinux
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
References 9
git.kernel.org
- stable/c/89bbead9d897c77d0b566349c8643030ff2abeba
- stable/c/0e4e2e60556c6ed00e8450b720f106a268d23062
- stable/c/dd70c8a89ef99c3d53127fe19e51ef47c3f860fa
- stable/c/e7a8442195e8ebd97df467ce4742980ab57edcce
- stable/c/9230a59eda0878d7ecaa901d876aec76f57bd455
- stable/c/7f64cb5b4d8c872296eda0fdce3bcf099eec7aa7
- stable/c/f032e1dac30b3376c7d6026fb01a8c403c47a80d
- stable/c/e914bf68dab88815a7ae7b7a3a5e8913c8ff14a5
- stable/c/8beee4d8dee76b67c75dc91fd8185d91e845c160