Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50243

sctp: handle the error returned from sctp_auth_asoc_init_active_key

High7.8EPSS 0.16%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2022-50243, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected 50b57223da67653c61e405d0a7592355cfe4585e – < b8fa99a3a11bdd77fef6b4a97f1021eb30b5ba40
    • affected b60461696a0b0fdaf240bc365b7983698f88ded2 – < 382ff44716603a54f5fd238ddec6a2468e217612
    • affected 8eb225873246312660ccd68296959a7b213d0cdd – < f65955340e0044f5c41ac799a01698ac7dee8a4e
    • affected 58acd10092268831e49de279446c314727101292 – < 19d636b663e0e92951bba5fced929ca7fd25c552
    • affected 58acd10092268831e49de279446c314727101292 – < 0f90099d18e3abdc01babf686f41f63fe04939c1
    • affected 58acd10092268831e49de279446c314727101292 – < 3b0fcf5e29c0940e1169ce9c44f73edd98bdf12d
    • affected 58acd10092268831e49de279446c314727101292 – < 022152aaebe116a25c39818a07e175a8cd3c1e11
    • affected c1de376423a7759bf4fa25d6a038a4c1e035c9e1
    • affected 4.19.199 – < 4.19.262
    • affected 5.4.136 – < 5.4.220
    • affected 5.10.54 – < 5.10.150
    • affected 5.13.6 – < 5.14
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 4.19.262 – ≤ 4.19.*
    • unaffected 5.4.220 – ≤ 5.4.*
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50243 badge
[![CVE-2022-50243](https://trackcve.app/badge/CVE-2022-50243.svg)](https://trackcve.app/cve/CVE-2022-50243)

Record last updated .