CVE-2025-23142sctp: detect and prevent references to a freed transport in sendmsg
Updated under an hour ago ()
Does this affect you?
It affects Linux and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: sctp: detect and prevent references to a freed transport in sendmsg sctp_sendmsg() re-uses associations and transports when possible by doing a lookup based on the socket endpoint and the message destination address, and then sctp_sendmsg_to_asoc() sets the selected transport in all the message chunks to be sent. There's a possible race condition if another thread triggers the removal of that selected transport, for instance, by explicitly unbinding an address with setsockopt(SCTP_SOCKOPT_BINDX_REM), after the chunks have been set up and before the message is sent. This can happen if the send buffer is full, during the period when the sender thread temporarily releases the socket lock in sctp_wait_for_sndbuf(). This causes the access to the transport data in sctp_outq_select_transport(), when the association outqueue is flushed, to result in a use-after-free read. This change avoids this scenario by having sctp_transport_free() signal the freeing of the transport, tagging it as "dead". In order to do this, the patch restores the "dead" bit in struct sctp_transport, which was removed in commit 47faa1e4c50e ("sctp: remove the dead field of sctp_transport"). Then, in the scenario where the sender thread has released the socket lock in sctp_wait_for_sndbuf(), the bit is checked again after re-acquiring the socket lock to detect the deletion. This is done while holding a reference to the transport to prevent it from being freed in the process. If the transport was deleted while the socket lock was relinquished, sctp_sendmsg_to_asoc() will return -EAGAIN to let userspace retry the send. The bug was found by a private syzbot instance (see the error report [1] and the C reproducer that triggers it [2]).
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from df132eff463873e14e019a07f387b4d577d6d1f9 before 547762250220325d350d0917a7231480e0f4142b; from df132eff463873e14e019a07f387b4d577d6d1f9 before 3257386be6a7eb8a8bfc9cbfb746df4eb4fc70e8; from df132eff463873e14e019a07f387b4d577d6d1f9 before 0f7df4899299ce4662e5f95badb9dbc57cc37fa5; from df132eff463873e14e019a07f387b4d577d6d1f9 before 7a63f4fb0efb4e69efd990cbb740a848679ec4b0; from df132eff463873e14e019a07f387b4d577d6d1f9 before c6fefcb71d246baaf3bacdad1af7ff50ebcfe652; from df132eff463873e14e019a07f387b4d577d6d1f9 before 9e7c37fadb3be1fc33073fcf10aa96d166caa697; from df132eff463873e14e019a07f387b4d577d6d1f9 before 5bc83bdf5f5b8010d1ca5a4555537e62413ab4e2; from df132eff463873e14e019a07f387b4d577d6d1f9 before 2e5068b7e0ae0a54f6cfd03a2f80977da657f1ee; and 11 more ranges | CNA record |
linux linux_kernel linux:linux_kernel | from 3.18.128 before 3.19; from 4.4.166 before 4.5; from 4.9.142 before 4.10; from 4.14.85 before 4.15; from 4.19.6 before 5.4.293; from 5.5 before 5.10.237; from 5.11 before 5.15.181; from 5.16 before 6.1.135; and 5 more ranges | NVD |
debian debian_linux debian:debian_linux | 11.0 | NVD |
References
- https://git.kernel.org/stable/c/547762250220325d350d0917a7231480e0f4142bpatch
- https://git.kernel.org/stable/c/3257386be6a7eb8a8bfc9cbfb746df4eb4fc70e8patch
- https://git.kernel.org/stable/c/0f7df4899299ce4662e5f95badb9dbc57cc37fa5patch
- https://git.kernel.org/stable/c/7a63f4fb0efb4e69efd990cbb740a848679ec4b0patch
- https://git.kernel.org/stable/c/c6fefcb71d246baaf3bacdad1af7ff50ebcfe652patch
- https://git.kernel.org/stable/c/9e7c37fadb3be1fc33073fcf10aa96d166caa697patch
- https://git.kernel.org/stable/c/5bc83bdf5f5b8010d1ca5a4555537e62413ab4e2patch
- https://git.kernel.org/stable/c/2e5068b7e0ae0a54f6cfd03a2f80977da657f1eepatch
- https://git.kernel.org/stable/c/f1a69a940de58b16e8249dff26f74c8cc59b32bepatch
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.htmlmailing-list, third-party-advisory
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.htmlmailing-list, third-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.