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-2026-46227sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months 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-2026-46227, 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
redhat-SADPADP (enrichment)3.1High7.0CVSS:3.1/AV:L/AC:H/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.10% · top 99% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < f3a3f0b406b4b7eb3cea35a23fa2bf170848b104
    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < 0dbc8cde64280fc37cdd678cced34eaf96cfb197
    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < 0c7b55974f97b78d1109025eadf084e74cbf330f
    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < 1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078
    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < 6187a172d6ed57d6b2c327836e4407c6456e639d
    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < c9dadb31f36045a8cb65df4bd75e7237ef21a4b5
    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < bf0f40d8107e2ce827521968dc6926f3e13728ae
    • affected 4910280503f3af2857d5aa77e35b22d93a8960a8 – < abb5f36771cc4c05899b34000829a787572a8817
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.90 – ≤ 6.12.*
    • unaffected 6.18.32 – ≤ 6.18.*
    • unaffected 7.0.9 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References31

Sources

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

Badge for a README or a ticket

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

Record last updated .