CVE Professor — Güvenlik Açığı Takip & Analiz
›
CVE-2026-80780

BELİRSİZ Güvenlik Açığı

BELİRSİZ CVSS 0 ⚡ EPSS 0.2% NVD

In the Linux kernel, the following vulnerability has been resolved: HID: pidff: fix OOB write when hid->inputs is empty hid_pidff_init_with_quirks() derives its input_dev from list_entry(hid->inputs.next, struct hid_input, list) without first checking that hid->inputs is non-empty. The list member of struct hid_input is at offset 0, so on an empty list list_entry() yields &hid->inputs itself and the following hidinput->input load reads an unrelated member of struct hid_device. dev is then a type-confused pointer, and force-feedback init writes through it: each set_bit(FF_*, dev->ffbit) stores 8 bytes at dev + 192, past the end of the object dev actually aliases, and input_ff_create() adds further writes of a heap pointer and two function pointers. Until hid-universal-pidff the only caller was hid_pidff_init() from usbhid, which runs under HID_CLAIMED_INPUT and therefore always has at least one hid_input. universal_pidff_probe() starts the device with HID_CONNECT_DEFAULT & ~HID_CONNECT_FF and then calls hid_pidff_init_with_quirks() directly whenever the descriptor carries a PID usage page, bypassing that gate. A report descriptor whose only application collection is on HID_UP_PID leaves hid->inputs empty while hid_connect() still succeeds through the hidraw claim, so probe reaches the unguarded list_entry(). The write happens in the USB probe path, on the hotplug workqueue, so plugging in a malicious device is enough to trigger it; no attacker software and no logged-in user are required. KASAN reports an 8-byte out-of-bounds write in hid_pidff_init_with_quirks() reached from universal_pidff_probe(). Check for an empty list before deriving dev and return -ENODEV, as the other HID force-feedback drivers already do. universal_pidff_probe() propagates the error and unwinds. Discovered by XBOW, triaged by Baul Lee <[email protected]>

Yayınlanma 04.09.2026
ISO Tarih 2026-09-04
Kaynak NVD
EPSS — Exploit Olasılık Skoru
0.2%
30 günlük olasılık
Tüm CVElerin 8. yüzdeliğinde — Bu açığın istismar edilme ihtimali çoğu CVEden yüksek.
AI Güvenlik Analizi

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-80780
CVSS 0/10 · BELİRSİZ · 04.09.2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 AÇIK NEDİR?
Buffer Overflow / Memory Corruption
Açıklama: In the Linux kernel, the following vulnerability has been resolved:

HID: pidff: fix OOB write when hid->inputs is empty

hid_pidff_init_with_quirks() derives its input_dev from

list_entry(hid->inputs.next, struct hid_input, list)

without first checking that hid->inputs is non-empty. The list member
of struct hid_input is at offset 0, so on an empty list list_entry()
yields &hid->inputs itse…

⚡ SALDIRI ZİNCİRİ
Saldırı adımları:
1. Fuzzing ile çöküş noktası tespit edilir: Boofuzz, AFL++ ile.
2. GDB/PEDA ile offset hesaplanır: pattern create 500 → crash → pattern offset EIP_VALUE
3. Stack/Heap layout analizi.
4. ROP gadget ile NX bypass.
5. Metasploit varsa: use exploit/... ; run

🔧 Araçlar: GDB+PEDA/pwndbg, ROPgadget, pwntools, Metasploit, AFL++
🗺️ MITRE ATT&CK: T1203 (Exploitation for Client Execution), T1068

🌍 GERÇEK DÜNYA ETKİSİ

🛡️ ÇÖZÜM VE MİTİGASYON
→ Üretici tarafından yayınlanan yamayı uygula.
→ ASLR/NX/Stack Canary aktif olduğunu kontrol et.
→ WAF kuralı ekle, anormal trafik için IDS alert oluştur.

⚠️ ACİLİYET
📌 Düşük öncelik — rutin güncelleme yeterli.

────────────────────────────────────────
[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ı]

Hedef Keşif Sorguları
CVSS Skoru
0 / 10 · CVSS BELİRSİZ