CVEvulnerability
CVE-2025-23142
7.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2025-05-01
- Last modified
- 2026-10-15
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-416
Description
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]).
Affected configurations
• linux linux kernel (>= 3.18.128 < 3.19)
• linux linux kernel (>= 4.4.166 < 4.5)
• linux linux kernel (>= 4.9.142 < 4.10)
• linux linux kernel (>= 4.14.85 < 4.15)
• linux linux kernel (>= 4.19.6 < 5.4.293)
• linux linux kernel (>= 5.5 < 5.10.237)
• linux linux kernel (>= 5.11 < 5.15.181)
• linux linux kernel (>= 5.16 < 6.1.135)
• linux linux kernel (>= 6.2 < 6.6.88)
• linux linux kernel (>= 6.7 < 6.12.24)
• linux linux kernel (>= 6.13 < 6.13.12)
• linux linux kernel (>= 6.14 < 6.14.3)
• linux linux kernel 6.15
• debian debian linux 11.0
Related
Weakness · CWE (1)
- CWE-416 Use After Free weakness
References
- https://git.kernel.org/stable/c/0f7df4899299ce4662e5f95badb9dbc57cc37fa5 Patch
- https://git.kernel.org/stable/c/2e5068b7e0ae0a54f6cfd03a2f80977da657f1ee Patch
- https://git.kernel.org/stable/c/3257386be6a7eb8a8bfc9cbfb746df4eb4fc70e8 Patch
- https://git.kernel.org/stable/c/547762250220325d350d0917a7231480e0f4142b Patch
- https://git.kernel.org/stable/c/5bc83bdf5f5b8010d1ca5a4555537e62413ab4e2 Patch
- https://git.kernel.org/stable/c/7a63f4fb0efb4e69efd990cbb740a848679ec4b0 Patch
- https://git.kernel.org/stable/c/9e7c37fadb3be1fc33073fcf10aa96d166caa697 Patch
- https://git.kernel.org/stable/c/c6fefcb71d246baaf3bacdad1af7ff50ebcfe652 Patch
- https://git.kernel.org/stable/c/f1a69a940de58b16e8249dff26f74c8cc59b32be Patch
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html Mailing List, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html Mailing List, Third Party Advisory