CVE-2022-50243
published 2025-09-15CVE-2022-50243: In the Linux kernel, the following vulnerability has been resolved: sctp: handle the error returned from sctp_auth_asoc_init_active_key When it returns an…
PriorityP337high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.15%
4.7th percentile
In the Linux kernel, the following vulnerability has been resolved:
sctp: handle the error returned from sctp_auth_asoc_init_active_key
When it returns an error from sctp_auth_asoc_init_active_key(), the
active_key is actually not updated. The old sh_key will be freeed
while it's still used as active key in asoc. Then an use-after-free
will be triggered when sending patckets, as found by syzbot:
sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112
sctp_set_owner_w net/sctp/socket.c:132 [inline]
sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863
sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025
inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819
sock_sendmsg_nosec net/socket.c:714 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:734
This patch is to fix it by not replacing the sh_key when it returns
errors from sctp_auth_asoc_init_active_key() in sctp_auth_set_key().
For sctp_auth_set_active_key(), old active_key_id will be set back
to asoc->active_key_id when the same thing happens.
Affected
26 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.3-1 (bookworm) | linux 6.0.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 4.19.199 < 4.19.262 | 4.19.262 |
| linux | linux | >= 5.10.54 < 5.10.150 | 5.10.150 |
| linux | linux | >= 5.13.6 < 5.14 | 5.14 |
| linux | linux | >= 5.4.136 < 5.4.220 | 5.4.220 |
| linux | linux | >= 50b57223da67653c61e405d0a7592355cfe4585e < b8fa99a3a11bdd77fef6b4a97f1021eb30b5ba40 | b8fa99a3a11bdd77fef6b4a97f1021eb30b5ba40 |
| linux | linux | >= 58acd10092268831e49de279446c314727101292 < 19d636b663e0e92951bba5fced929ca7fd25c552 | 19d636b663e0e92951bba5fced929ca7fd25c552 |
| linux | linux | >= 58acd10092268831e49de279446c314727101292 < 0f90099d18e3abdc01babf686f41f63fe04939c1 | 0f90099d18e3abdc01babf686f41f63fe04939c1 |
| linux | linux | >= 58acd10092268831e49de279446c314727101292 < 3b0fcf5e29c0940e1169ce9c44f73edd98bdf12d | 3b0fcf5e29c0940e1169ce9c44f73edd98bdf12d |
| linux | linux | >= 58acd10092268831e49de279446c314727101292 < 022152aaebe116a25c39818a07e175a8cd3c1e11 | 022152aaebe116a25c39818a07e175a8cd3c1e11 |
| linux | linux | >= 8eb225873246312660ccd68296959a7b213d0cdd < f65955340e0044f5c41ac799a01698ac7dee8a4e | f65955340e0044f5c41ac799a01698ac7dee8a4e |
| linux | linux | >= b60461696a0b0fdaf240bc365b7983698f88ded2 < 382ff44716603a54f5fd238ddec6a2468e217612 | 382ff44716603a54f5fd238ddec6a2468e217612 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 0 < 6.0.3-1 | 6.0.3-1 |
| linux | linux_kernel | >= 4.19.199 < 4.19.262 | 4.19.262 |
| linux | linux_kernel | >= 5.10.54 < 5.10.150 | 5.10.150 |
| linux | linux_kernel | >= 5.13.6 < 5.14 | 5.14 |
| linux | linux_kernel | >= 5.14.1 < 5.15.75 | 5.15.75 |
| linux | linux_kernel | >= 5.16 < 5.19.17 | 5.19.17 |
| linux | linux_kernel | >= 5.4.136 < 5.4.220 | 5.4.220 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-2hwr-p3mh-h7f6: In the Linux kernel, the following vulnerability has been resolved:
sctp: handle the error returned from sctp_auth_asoc_init_active_key
When it retu
ghsa_unreviewed·2025-09-15
CVE-2022-50243 [HIGH] CWE-416 GHSA-2hwr-p3mh-h7f6: In the Linux kernel, the following vulnerability has been resolved:
sctp: handle the error returned from sctp_auth_asoc_init_active_key
When it retu
In the Linux kernel, the following vulnerability has been resolved:
sctp: handle the error returned from sctp_auth_asoc_init_active_key
When it returns an error from sctp_auth_asoc_init_active_key(), the
active_key is actually not updated. The old sh_key will be freeed
while it's still used as active key in asoc. Then an use-after-free
will be triggered when sending patckets, as found by syzbot:
sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112
sctp_set_owner_w net/sctp/socket.c:132 [inline]
sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863
sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025
inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819
sock_sendmsg_nosec net/socket.c:714 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:734
This patch is to fix it by not replacing the sh_key when it
OSV
CVE-2022-50243: In the Linux kernel, the following vulnerability has been resolved: sctp: handle the error returned from sctp_auth_asoc_init_active_key When it return
osv·2025-09-15·CVSS 7.8
CVE-2022-50243 [HIGH] CVE-2022-50243: In the Linux kernel, the following vulnerability has been resolved: sctp: handle the error returned from sctp_auth_asoc_init_active_key When it return
In the Linux kernel, the following vulnerability has been resolved: sctp: handle the error returned from sctp_auth_asoc_init_active_key When it returns an error from sctp_auth_asoc_init_active_key(), the active_key is actually not updated. The old sh_key will be freeed while it's still used as active key in asoc. Then an use-after-free will be triggered when sending patckets, as found by syzbot: sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112 sctp_set_owner_w net/sctp/socket.c:132 [inline] sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863 sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025 inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:734 This patch is to fix it by not replacing the sh_key when it ret
Red Hat
kernel: sctp: handle the error returned from sctp_auth_asoc_init_active_key
vendor_redhat·2025-09-15·CVSS 7.8
CVE-2022-50243 [HIGH] CWE-324 kernel: sctp: handle the error returned from sctp_auth_asoc_init_active_key
kernel: sctp: handle the error returned from sctp_auth_asoc_init_active_key
In the Linux kernel, the following vulnerability has been resolved:
sctp: handle the error returned from sctp_auth_asoc_init_active_key
When it returns an error from sctp_auth_asoc_init_active_key(), the
active_key is actually not updated. The old sh_key will be freeed
while it's still used as active key in asoc. Then an use-after-free
will be triggered when sending patckets, as found by syzbot:
sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112
sctp_set_owner_w net/sctp/socket.c:132 [inline]
sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863
sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025
inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819
sock_sendmsg_nosec net/socket.c:714 [inline]
sock_sendmsg+0xcf/0x120 net
Debian
CVE-2022-50243: linux - In the Linux kernel, the following vulnerability has been resolved: sctp: handl...
vendor_debian·2022·CVSS 7.8
CVE-2022-50243 [HIGH] CVE-2022-50243: linux - In the Linux kernel, the following vulnerability has been resolved: sctp: handl...
In the Linux kernel, the following vulnerability has been resolved: sctp: handle the error returned from sctp_auth_asoc_init_active_key When it returns an error from sctp_auth_asoc_init_active_key(), the active_key is actually not updated. The old sh_key will be freeed while it's still used as active key in asoc. Then an use-after-free will be triggered when sending patckets, as found by syzbot: sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112 sctp_set_owner_w net/sctp/socket.c:132 [inline] sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863 sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025 inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:734 This patch is to fix it by not replacing the sh_key when it ret
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/022152aaebe116a25c39818a07e175a8cd3c1e11https://git.kernel.org/stable/c/0f90099d18e3abdc01babf686f41f63fe04939c1https://git.kernel.org/stable/c/19d636b663e0e92951bba5fced929ca7fd25c552https://git.kernel.org/stable/c/382ff44716603a54f5fd238ddec6a2468e217612https://git.kernel.org/stable/c/3b0fcf5e29c0940e1169ce9c44f73edd98bdf12dhttps://git.kernel.org/stable/c/b8fa99a3a11bdd77fef6b4a97f1021eb30b5ba40https://git.kernel.org/stable/c/f65955340e0044f5c41ac799a01698ac7dee8a4e
2025-09-15
Published