Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-46999sctp: do asoc update earlier in sctp_sf_do_dupcook_a

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: do asoc update earlier in sctp_sf_do_dupcook_a There's a panic that occurs in a few of envs, the call trace is as below: [] general protection fault, ... 0x29acd70f1000a: 0000 [#1] SMP PTI [] RIP: 0010:sctp_ulpevent_notify_peer_addr_change+0x4b/0x1fa [sctp] [] sctp_assoc_control_transport+0x1b9/0x210 [sctp] [] sctp_do_8_2_transport_strike.isra.16+0x15c/0x220 [sctp] [] sctp_cmd_interpreter.isra.21+0x1231/0x1a10 [sctp] [] sctp_do_sm+0xc3/0x2a0 [sctp] [] sctp_generate_timeout_event+0x81/0xf0 [sctp] This is caused by a transport use-after-free issue. When processing a duplicate COOKIE-ECHO chunk in sctp_sf_do_dupcook_a(), both COOKIE-ACK and SHUTDOWN chunks are allocated with the transort from the new asoc. However, later in the sideeffect machine, the old asoc is used to send them out and old asoc's shutdown_last_sent_to is set to the transport that SHUTDOWN chunk attached to in sctp_cmd_setup_t2(), which actually belongs to the new asoc. After the new_asoc is freed and the old asoc T2 timeout, the old asoc's shutdown_last_sent_to that is already freed would be accessed in sctp_sf_t2_timer_expire(). Thanks Alexander and Jere for helping dig into this issue. To fix it, this patch is to do the asoc update first, then allocate the COOKIE-ACK and SHUTDOWN chunks with the 'updated' old asoc. This would make more sense, as a chunk from an asoc shouldn't be sent out with another asoc. We had fixed quite a few issues caused by this.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-46999, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/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.74% · top 45% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected db8bf823e70f239372c62f13e4eb6f08a1665e8c – < d624f2991b977821375fbd56c91b0c91d456a697
    • affected a204d577be70e0a0a6023cf1b9859c9ebffaeecd – < b1b31948c0af44628e43353828453461bb74098f
    • affected 145cb2f7177d94bc54563ed26027e952ee0ae03c – < f01988ecf3654f805282dce2d3bb9afe68d2691e
    • affected 145cb2f7177d94bc54563ed26027e952ee0ae03c – < 61b877bad9bb0d82b7d8841be50872557090a704
    • affected 145cb2f7177d94bc54563ed26027e952ee0ae03c – < 0bfd913c2121b3d553bfd52810fe6061d542d625
    • affected 145cb2f7177d94bc54563ed26027e952ee0ae03c – < 35b4f24415c854cd718ccdf38dbea6297f010aae
    • affected a5ce8531ea508d270822b2bc6140c6198c8a2a7b
    • affected 4.19.123 – < 4.19.191
    • affected 5.4.41 – < 5.4.120
    • affected 5.6.13 – < 5.7
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 4.19.191 – ≤ 4.19.*
    • unaffected 5.4.120 – ≤ 5.4.*
    • unaffected 5.10.38 – ≤ 5.10.*
    • unaffected 5.11.22 – ≤ 5.11.*
    • unaffected 5.12.5 – ≤ 5.12.*
    • unaffected 5.13 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

CVE-2021-46999 badge
[![CVE-2021-46999](https://cveledger.app/badge/CVE-2021-46999.svg)](https://cveledger.app/cve/CVE-2021-46999)

Record last updated .