KRİTİK Güvenlik Açığı
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-74587
CVSS 9.8/10 · KRİTİK · 22.08.2026
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 AÇIK NEDİR?
Açıklama: 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.
⚡ SALDIRI ZİNCİRİ
İnternet üzerinden uzaktan | kimlik doğrulama GEREKMİYOR | kullanıcı etkileşimi YOK | düşük karmaşıklık.
🌍 GERÇEK DÜNYA ETKİSİ
Tüm gizli veriler okunabilir/çalınabilir; sistem verileri değiştirilebilir/silinebilir; hizmet tamamen devre dışı bırakılabilir.
🛡️ ÇÖZÜM VE MİTİGASYON
→ Üretici tarafından yayınlanan yamayı uygula.
→ Yama öncesi: servis erişimini VPN arkasına al veya IP whitelist uygula.
→ WAF kuralı ekle, anormal trafik için IDS alert oluştur.
⚠️ ACİLİYET
🚨 HEMEN (24-48 saat) — Uzaktan, kimlik doğrulamasız, düşük karmaşıklık.
────────────────────────────────────────
[Kural Tabanlı Analiz] [💡 config.json dosyasına ai_key (Claude: sk-ant-... veya Groq: gsk_...) ekleyerek gerçek AI analizi kullanabilirsiniz]
[⚠️ AI key mevcut ancak istek başarısız — kural tabanlı analiz kullanıldı]