YÜKSEK Güvenlik Açığı
In the Linux kernel, the following vulnerability has been resolved: dm-pcache: validate kset key_num and intra-segment bounds Two more fields decoded from the cache device go unbounded. The kset key_num drives cache_kset_crc() and the replay loop in cache_replay(), the writeback worker and the GC worker, but only the magic and a fixed-seed CRC are checked first, so a non-last kset whose key_num exceeds the PCACHE_KSET_KEYS_MAX buffer reads past its end before the CRC compare. A key's intra-segment offset and length in cache_key_decode() are taken verbatim, so a key running past its segment is replayed into the cache tree and the data CRC check and every later read hit then copy adjacent persistent memory into the caller's bio -- an out-of-bounds read that leaks to user space. Both fields are controlled by whoever supplies the cache device (CAP_SYS_ADMIN); the CRC seed is public. Add kset_onmedia_valid() to bound key_num before any kset read, and reject a key whose offset plus length, computed in 64 bits, exceeds the segment data_size. Valid metadata is unaffected.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-80961
CVSS 7.8/10 · YÜKSEK · 11.09.2026
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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:
dm-pcache: validate kset key_num and intra-segment bounds
Two more fields decoded from the cache device go unbounded. The kset
key_num drives cache_kset_crc() and the replay loop in cache_replay(),
the writeback worker and the GC worker, but only the magic and a
fixed-seed CRC are checked first, so a non-last kset whose key_n…
⚡ SALDIRI ZİNCİRİ
Yerel/fiziksel erişim | düşük yetkili hesap | 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.
→ 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ı]