CVE-2026-74587

CVE CVE-2026-74587EUVD EUVD-2026-64524Published 2026-08-22T15:31:39.000ZLast changed 2026-08-25T05:40:13.000ZCVSS 9.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux a000c01e60e40e15304ffe48fff051d17a7bea91 <dc67d528c2fa939cec7fe3bf7f3089c8d281ca3d; patch: 5.10.265; a000c01e60e40e15304ffe48fff051d17a7bea91 <618b5c6d049896fcfabb91afc072954c92cb2693; patch: 5.15.216; a000c01e60e40e15304ffe48fff051d17a7bea91 <10459b03e2d9ee12435e96f587de4d4cacdbf435; patch: 6.1.183; a000c01e60e40e15304ffe48fff051d17a7bea91 <179676f0166230c80053a392303485b37c93dd33; patch: 7.1.9; patch: 6.6.152; 3.0; a000c01e60e40e15304ffe48fff051d17a7bea91 <8c283e7b56adce00193837f3311b06662466fb21; a000c01e60e40e15304ffe48fff051d17a7bea91 <d949992bc3f00027a2c755e860a11950c75f6073; a000c01e60e40e15304ffe48fff051d17a7bea91 <07daf4f9750104960a1d60831b2353c0d41f35fb; a000c01e60e40e15304ffe48fff051d17a7bea91 <e1bb114e09372fd6e03387ced9ef566da336ed6c; patch: 6.18.45; patch: 6.12.104; patch: 0; patch: 7.2

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.