CVE-2026-89479

CVE CVE-2026-89479EUVD EUVD-2026-76385Veröffentlicht 2026-09-11T19:43:35.000ZZuletzt geändert 2026-09-14T12:00:16.000ZCVSS 9.8

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: sctp: stop processing a packet once its association is deleted sctp_endpoint_bh_rcv() looks the association up only when chunk->asoc is NULL, and caches the result in chunk->asoc and chunk->transport without taking a reference. A packet that matches no association is handed to the endpoint, so a peer can bundle COOKIE ECHO, SHUTDOWN and SHUTDOWN ACK in one packet. The COOKIE ECHO creates the association, the SHUTDOWN chunk caches it, and with the outqueue empty the SHUTDOWN ACK reaches sctp_sf_do_9_2_final(), so the association and its transports are freed. The endpoint loop has no counterpart to the asoc->base.dead check in sctp_assoc_bh_rcv(). The next chunk writes to last_time_heard in the freed transport and is then passed to sctp_do_sm() with the freed association. The transport is freed through RCU, so this needs the packet to come off the socket backlog, where the loop runs in task context. The endpoint loop cannot do the same check: it holds no reference on the association, so reading asoc->base.dead would itself be a use-after-free. Mark the packet for discard in the command interpreter, just before it deletes the association. That is also before sctp_inq_free() releases the chunk on the association receive path. sctp_sf_do_5_2_4_dupcook() issues SCTP_CMD_DELETE_TCB for the temporary association, while the one the packet belongs to stays alive. A restarting peer can bundle DATA behind its COOKIE ECHO, so compare against chunk->asoc and leave that case alone.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a713e1b3a265f180ad25a08e17be15d67a2f7149; patch: 6.6.157; 2.6.12; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fa306a40e716c5abcd967475459ce1ebd56e5115; patch: 7.3-rc1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <09c3b193a3e8fe53e1f416e2f8e3283d2a785405; patch: 5.15.221; patch: 0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5c0b2dbbdafc9eeeb11fffe1e46551fc3b55d8ee; patch: 7.2.4; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d970353eeb98f46a3b9dc602850e4f6336a9889; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed85fe91a61bc0e0da6b585c07102b20f4cc65a0; patch: 6.12.109; patch: 6.1.188; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47e15a8d12e366d0d261bcbc394394f44418938d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee3f04cf566f6041aa9a0360494fd8db5ade383a; patch: 5.10.270; patch: 6.18.50

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.