YÜKSEK Güvenlik Açığı
In the Linux kernel, the following vulnerability has been resolved: vsock/vmci: validate packet source for connected sockets vmci_transport_recv_stream_cb() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback can select a non-listening socket without checking whether the packet came from its stored peer. This was reproduced with two VMCI contexts. A RST from the context not stored in a TCP_SYN_SENT socket reset that socket after it was selected by the destination-only lookup. VMCI can process notification packets in bottom-half context when the socket is not owned by user context, or defer packets to a workqueue. Use vsock_check_source() after taking the socket lock in the bottom-half path, and recheck after lock_sock() in the workqueue path. Listening sockets continue to accept packets from any source. Reply with a RST addressed from the received packet before dropping a source that fails validation. This preserves the existing reset behavior for bound non-listening and concurrently closed sockets without directing the reset to a connected socket's stored peer.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-99122
CVSS 7.3/10 · YÜKSEK · 28.10.2026
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 AÇIK NEDİR?
Açıklama: In the Linux kernel, the following vulnerability has been resolved:
vsock/vmci: validate packet source for connected sockets
vmci_transport_recv_stream_cb() looks up sockets first by the full source
and destination tuple, then by destination only in the bound table. The
fallback can select a non-listening socket without checking whether the
packet came from its stored peer. This was reproduce…
⚡ SALDIRI ZİNCİRİ
Yerel/fiziksel erişim | düşük yetkili hesap | kullanıcı etkileşimi YOK | düşük karmaşıklık.
⚠️ Scope değişiyor — etki diğer sistemlere sıçrayabilir.
🌍 GERÇEK DÜNYA ETKİSİ
Hizmet tamamen devre dışı bırakılabilir; diğer sistemlere pivot mümkün.
🛡️ ÇÖZÜM VE MİTİGASYON
→ Üretici tarafından yayınlanan yamayı uygula.
→ WAF kuralı ekle, anormal trafik için IDS alert oluştur.
⚠️ ACİLİYET
⚠️ Planlı bakım (2 hafta) — Yüksek seviye.
────────────────────────────────────────
[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ı]