CVE-2025-39812 — sctp: initialize more fields in sctp_v6_from_sk()
In the Linux kernel, the following vulnerability has been resolved: sctp: initialize more fields in sctp_v6_from_sk() syzbot found that sin6_scope_id was not properly initialized, leading to undefined behavior. Clear sin6_scope_id and sin6_flowinfo. BUG: KMSAN: uninit-value in __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 __sctp_v6_cmp_addr+0x887/0x8c0 net/sctp/ipv6.c:649 sctp_inet6_cmp_addr+0x4f2/0x510 net/sctp/ipv6.c:983 sctp_bind_addr_conflict+0x22a/0x3b0 net/sctp/bind_addr.c:390 sctp_get_port_local+0x21eb/0x2440 net/sctp/socket.c:8452 sctp_get_port net/sctp/socket.c:8523 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x710/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930 x64_sys_call+0x271d/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:51 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Local variable addr.i.i created at: sctp_get_port net/sctp/socket.c:8515 [inline] sctp_listen_start net/sctp/socket.c:8567 [inline] sctp_inet_listen+0x650/0xfd0 net/sctp/socket.c:8636 __sys_listen_socket net/socket.c:1912 [inline] __sys_listen net/socket.c:1927 [inline] __do_sys_listen net/socket.c:1932 [inline] __se_sys_listen net/socket.c:1930 [inline] __x64_sys_listen+0x343/0x4c0 net/socket.c:1930
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 11.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux |
version 2.6.12≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 2e8750469242cad8f01f320131fd5a6f540dbb99≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f6c2cc99fc2387ba6499facd6108f6543382792d≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 1bbc0c02aea1f1c405bd1271466889c25a1fe01b≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 463aa96fca6209bb205f49f7deea3817d7ddaa3a≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 65b4693d8bab5370cfcb44a275b4d8dcb06e56bf≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 17d6c7747045e9b802c2f5dfaba260d309d831ae≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 9546934c2054bba1bd605c44e936619159a34027 and 1 more≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 45e4b36593edffb7bbee5828ae820bc10a9fa0f3 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 2.6.12-rc5version 6.17-rc3version 6.17-rc2version 6.17-rc1version 2.6.12-rc4version 2.6.12-rc3version 2.6.12-rc2version 2.6.12 and 7 more≥ 6.13 and < 6.16.5≥ 6.7 and < 6.12.45≥ 6.2 and < 6.6.104≥ 5.16 and < 6.1.150≥ 5.11 and < 5.15.191≥ 5.5 and < 5.10.242≥ 2.6.12.1 and < 5.4.298 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- Affected products added · linux/linux kernel, debian/debian linux
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 19, 2026 – Oct 19, 2026
References
13 on the record
- git.kernel.org/stable/c/463aa96fca6209bb205f49f7deea3817d7ddaa3a
- git.kernel.org/stable/c/9546934c2054bba1bd605c44e936619159a34027
- git.kernel.org/stable/c/1bbc0c02aea1f1c405bd1271466889c25a1fe01b
- git.kernel.org/stable/c/f6c2cc99fc2387ba6499facd6108f6543382792d
- git.kernel.org/stable/c/17d6c7747045e9b802c2f5dfaba260d309d831ae
- git.kernel.org/stable/c/45e4b36593edffb7bbee5828ae820bc10a9fa0f3
- git.kernel.org/stable/c/2e8750469242cad8f01f320131fd5a6f540dbb99
- git.kernel.org/stable/c/65b4693d8bab5370cfcb44a275b4d8dcb06e56bf
- github.com/advisories/GHSA-39p8-x6c9-fprr
- cert-portal.siemens.com/productcert/html/ssa-032379.html
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- nvd.nist.gov/vuln/detail/CVE-2025-39812
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 1d
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 1d
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-39812 is "sctp: initialize more fields in sctp_v6_from_sk()", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.