sctp: drop a chunk if its transport was removed (Linux Linux)
En bref
- Source
- NVD
- EPSS
- EPSS 0.51 % · centile 44 ()
- État
- PUBLISHED
- Publiée
- Mise à jour
- Attribuée par
- Linux
- Statut NVD
- Received
Description
In the Linux kernel, the following vulnerability has been resolved: sctp: drop a chunk if its transport was removed sctp_rcv() resolves the transport once per packet and leaves it in chunk->transport. The lookup reference, or the one sctp_add_backlog() takes if the socket is owned by userspace, keeps it around until the chunk has been processed. An authenticated ASCONF DEL-IP can remove it in the meantime. sctp_assoc_rm_peer() takes the transport out of the association and calls sctp_transport_free(), which tags it dead and drops the reference the association held. There is a window on both paths: the packet can sit on the socket backlog, and on the direct path the lookup completes before bh_lock_sock(). The DATA chunk in that packet puts the removed transport back into asoc->peer.last_data_from. Once the packet is done that reference goes away and the transport is freed by RCU, so the next delayed SACK carries the pointer into the SACK chunk and sctp_outq_select_transport() reads the freed transport's state. Drop the chunk in sctp_inq_push(), next to the existing rcvr->dead check. Both paths reach it with the association's socket lock held. The peer retransmits it.
Références
- https://git.kernel.org/stable/c/3fc072e7cb4a0ff251d13cfc2d24f62489cd9386
- https://git.kernel.org/stable/c/d7cb5ad832095dc4becfdb2a36007ffd50e49fb0
- https://git.kernel.org/stable/c/0422b092a3d43ca462932ff9f747731ca078d1d4
- https://git.kernel.org/stable/c/928fd7920ba37cc5637a211b9be979083413a2fa
- https://git.kernel.org/stable/c/c6c86a5e62a4fec36692ddd64b9144b660f71f96
- https://git.kernel.org/stable/c/1035bdef1efb9b1076d1a57b81e08c637ff08ecc
- https://git.kernel.org/stable/c/3537961df2163258bddc230db0e18dc14e925ea6
- https://git.kernel.org/stable/c/03a9d10ecf71f54b2af8020935f2033d4a132be5
Scores
| Version | Score | Vecteur | Évalué par |
|---|---|---|---|
| CVSS 3.1 | CRITICAL 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | Linux |
| CVSS 3.1 | CRITICAL 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | NVD · 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Secondary) |
Références européennes
- ENISA EUVD · EUVD-2026-76384
- GCVE · GCVE-0-2026-89478
Avis du CERT-FR
- CERTFR-2026-AVI-1385 — Multiples vulnérabilités dans les produits VMware · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1375 — Multiples vulnérabilités dans le noyau Linux de Debian LTS · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1289 — Multiples vulnérabilités dans le noyau Linux de Debian LTS · cert.ssi.gouv.fr
- CERTFR-2026-AVI-1253 — Multiples vulnérabilités dans le noyau Linux de Debian · cert.ssi.gouv.fr
Produits affectés
| Produit | Versions |
|---|---|
| Linux · Linux | affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 3fc072e7cb4a0ff251d13cfc2d24f62489cd9386 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d7cb5ad832095dc4becfdb2a36007ffd50e49fb0 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0422b092a3d43ca462932ff9f747731ca078d1d4 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 928fd7920ba37cc5637a211b9be979083413a2fa ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c6c86a5e62a4fec36692ddd64b9144b660f71f96 ; affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1035bdef1efb9b1076d1a57b81e08c637ff08ecc |
| Linux · Linux | affected 2.6.12 ; unaffected 0 < 2.6.12 ; unaffected 5.10.270 ≤ 5.10.* ; unaffected 5.15.221 ≤ 5.15.* ; unaffected 6.1.188 ≤ 6.1.* ; unaffected 6.6.157 ≤ 6.6.* |
Sources
| Source | Licence |
|---|---|
| CVE List (CVEProject cvelistV5) | CVE Program Terms of Use |
| EPSS (FIRST.org) | FIRST — attribution requested |
| ENISA EUVD | ENISA — reproduction authorised, source acknowledged |
| CERT-FR (ANSSI) | Licence Ouverte / Etalab 2.0 |
| NVD (NIST) via fkie-cad/nvd-json-data-feeds | Public domain — this product uses data from the NVD API but is not endorsed or certified by the NVD |