CVE-2025-23142: sctp: detect and prevent references to a freed transport in sendmsg
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0f7df4899299ce4662e5f95badb9dbc57cc37fa5, 2e5068b7e0ae0a54f6cfd03a2f80977da657f1ee, 3.19; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
Low priority for now. Upgrade to Linux Linux 0f7df4899299ce4662e5f95badb9dbc57cc37fa5, 2e5068b7e0ae0a54f6cfd03a2f80977da657f1ee, 3.19; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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]).
- Published
- May 1, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel4.4.166 and later · before 4.5
- linux linux kernel4.9.142 and later · before 4.10
- linux linux kernel4.14.85 and later · before 4.15
- linux linux kernel4.19.6 and later · before 5.4.293
- linux linux kernel5.5 and later · before 5.10.237
- linux linux kernel5.11 and later · before 5.15.181
- linux linux kernel3.18.128 and later · before 3.19
- linux linux kernel6.2 and later · before 6.6.88
- linux linux kernel6.7 and later · before 6.12.24
- linux linux kernel6.13 and later · before 6.13.12
- linux linux kernel6.14 and later · before 6.14.3
- linux linux kernel5.16 and later · before 6.1.135
- linux linux kernel6.15
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 26e51e5287eed4d96ea66a3da95429f42940f013, 8b97e045bd6d37f96f161e4d371ae174148e1587, e044554e97e812eb257d073bcc130e0ea653858f, 8376fdc999be008f0e9918db52f1ed8c08f5a1c9, cd947138e8c31e8cfcd489c12e9b97271beb6e79, 4.20affected
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before 547762250220325d350d0917a7231480e0f4142baffected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before 3257386be6a7eb8a8bfc9cbfb746df4eb4fc70e8affected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before 0f7df4899299ce4662e5f95badb9dbc57cc37fa5affected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before 7a63f4fb0efb4e69efd990cbb740a848679ec4b0affected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before c6fefcb71d246baaf3bacdad1af7ff50ebcfe652affected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before 9e7c37fadb3be1fc33073fcf10aa96d166caa697affected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before 5bc83bdf5f5b8010d1ca5a4555537e62413ab4e2affected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before 2e5068b7e0ae0a54f6cfd03a2f80977da657f1eeaffected · git
- df132eff463873e14e019a07f387b4d577d6d1f9 and later · before f1a69a940de58b16e8249dff26f74c8cc59b32beaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.135-1 | 6.1.135-1 |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
| Red Hat:rhel_e4s:9.0::appstream | bpftool-debuginfo | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-debuginfo | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-devel | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debug-devel-matched | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-devel | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-devel-matched | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-doc | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-tools-debuginfo | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-devel | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | perf | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | perf-debuginfo | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::appstream | python3-perf-debuginfo | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | bpftool | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | kernel | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
| Red Hat:rhel_e4s:9.0::baseos | kernel-abi-stablelists | before 0:5.14.0-70.161.1.el9_0 | 0:5.14.0-70.161.1.el9_0 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49931May 1, 2025 · IB/hfi1: Correctly move list in sc_disable()22Monitor
- ← EarlierCVE-2025-23141May 1, 2025 · KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses22Monitor
- Later →CVE-2025-23143May 1, 2025 · net: Fix null-ptr-deref by sock_lock_init_class_and_name() and rmmod.22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f7df4899299ce4662e5f95badb9dbc57cc37fa5 | Vendor (CNA) |
| Linux Linux | 2e5068b7e0ae0a54f6cfd03a2f80977da657f1ee | Vendor (CNA) |
| Linux Linux | 3.19 | Vendor (CNA) |
| Linux Linux | 3257386be6a7eb8a8bfc9cbfb746df4eb4fc70e8 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 547762250220325d350d0917a7231480e0f4142b | Vendor (CNA) |
| Linux Linux | 5bc83bdf5f5b8010d1ca5a4555537e62413ab4e2 | Vendor (CNA) |
| Linux Linux | 7a63f4fb0efb4e69efd990cbb740a848679ec4b0 | Vendor (CNA) |
| Linux Linux | 9e7c37fadb3be1fc33073fcf10aa96d166caa697 | Vendor (CNA) |
| Linux Linux | c6fefcb71d246baaf3bacdad1af7ff50ebcfe652 | Vendor (CNA) |
| Linux Linux | f1a69a940de58b16e8249dff26f74c8cc59b32be | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.135-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-570.77.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- git.kernel.org/stable/c/2e5068b7e0ae0a54f6cfd03a2f80977da657f1ee
- git.kernel.org/stable/c/3257386be6a7eb8a8bfc9cbfb746df4eb4fc70e8
- git.kernel.org/stable/c/547762250220325d350d0917a7231480e0f4142b
- git.kernel.org/stable/c/5bc83bdf5f5b8010d1ca5a4555537e62413ab4e2
- git.kernel.org/stable/c/7a63f4fb0efb4e69efd990cbb740a848679ec4b0
- git.kernel.org/stable/c/9e7c37fadb3be1fc33073fcf10aa96d166caa697
- git.kernel.org/stable/c/c6fefcb71d246baaf3bacdad1af7ff50ebcfe652
- git.kernel.org/stable/c/f1a69a940de58b16e8249dff26f74c8cc59b32be
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.