CVE-2026-74587 in the critical feed json
sctp: fix use-after-free of cached ASCONF chunk
published 2026-08-22 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-64524
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
sctp: fix use-after-free of cached ASCONF chunk
addip_last_asconf caches the outstanding outbound ASCONF chunk. The normal ASCONF-ACK completion path releases the chunk and clears the pointer.
However, sctp_asconf_queue_teardown() releases the cached chunk without clearing addip_last_asconf. During peer restart handling, sctp_sf_do_dupcook_a() queues SCTP_CMD_PURGE_ASCONF_QUEUE, which invokes sctp_asconf_queue_teardown() while the association remains alive and leaves the pointer dangling.
A delayed authenticated ASCONF-ACK can then reach sctp_sf_do_asconf_ack(), which accesses the stale chunk and passes it to sctp_process_asconf_ack(), causing a use-after-free and a second release.
Clearing the pointer exposes a race with T4 expiry. Peer restart handling queues the timer stop before the purge, but SCTP_CMD_TIMER_STOP uses timer_delete(), which does not wait for a callback already running on another CPU. Such a callback can reach sctp_sf_t4_timer_expire() after the purge and dereference NULL.
Clear addip_last_asconf after releasing the cached chunk, and make sctp_sf_t4_timer_expire() consume a stale T4 expiry if no outstanding ASCONF remains.
Patch / fix
- Linux Linux 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45, 7.1.9, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.105-1
- linux Debian 14 7.1.9-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-74587
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1113.119
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1111.115
ubuntu advisories UBUNTU-CVE-2026-74587
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-rt SLE Micro 5.4 5.14.21-150400.15.192.2
- kernel-source-rt SLE Micro 5.4 5.14.21-150400.15.192.2
- kernel-rt SLE Micro 5.5 5.14.21-150500.13.167.2
- kernel-source-rt SLE Micro 5.5 5.14.21-150500.13.167.2
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.246.1
suse advisories SUSE-SU-2026:4940-1SUSE-SU-2026:4939-1SUSE-SU-2026:4938-1SUSE-SU-2026:4937-1SUSE-SU-2026:4936-1SUSE-SU-2026:4935-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.40.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.40.1
opensuse advisories openSUSE-SU-2026:22167-1
- git.kernel.org/stable/c/10459b03e2d9ee12435e96f587de4d4cacdbf435 commit
- git.kernel.org/stable/c/e1bb114e09372fd6e03387ced9ef566da336ed6c commit
- git.kernel.org/stable/c/179676f0166230c80053a392303485b37c93dd33 commit
- git.kernel.org/stable/c/dc67d528c2fa939cec7fe3bf7f3089c8d281ca3d commit
- git.kernel.org/stable/c/618b5c6d049896fcfabb91afc072954c92cb2693 commit
- git.kernel.org/stable/c/07daf4f9750104960a1d60831b2353c0d41f35fb commit
- git.kernel.org/stable/c/d949992bc3f00027a2c755e860a11950c75f6073 commit
- git.kernel.org/stable/c/8c283e7b56adce00193837f3311b06662466fb21 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-74587 updated cvss 7.0
kernel: sctp: fix use-after-free of cached ASCONF chunk
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreunder investigation
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/10459b03e2d9ee12435e96f587de4d4cacdbf435
- git.kernel.org /stable/c/e1bb114e09372fd6e03387ced9ef566da336ed6c
- git.kernel.org /stable/c/179676f0166230c80053a392303485b37c93dd33
- git.kernel.org /stable/c/dc67d528c2fa939cec7fe3bf7f3089c8d281ca3d
- git.kernel.org /stable/c/618b5c6d049896fcfabb91afc072954c92cb2693
- git.kernel.org /stable/c/07daf4f9750104960a1d60831b2353c0d41f35fb
- git.kernel.org /stable/c/d949992bc3f00027a2c755e860a11950c75f6073
- git.kernel.org /stable/c/8c283e7b56adce00193837f3311b06662466fb21
Sources
- CVE List CVE-2026-74587
- NVD CVE-2026-74587
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.