Answer in brief
CVE-2026-64366 records a High severity (CVSS 8.8) vulnerability in HID: wacom: fix slab-out-of-bounds write in wacom_wac_queue_insert. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5e013ad206895e72d7da41bc1ae89d8cb499c3aa <ca899a926c11a59211b764b0155d9a1cdcc32b81 || >=5e013ad206895e72d7da41bc1ae89d8cb499c3aa <57bdd10ad50d68341f500a7b330f0d8949e510ec || >=5e013ad206895e72d7da41bc1ae89d8cb499c3aa <6b3014ec0e9a390ca563030b2d7689921f0daef5 | ca899a926c11a59211b764b0155d9a1cdcc32b81, 57bdd10ad50d68341f500a7b330f0d8949e510ec, 6b3014ec0e9a390ca563030b2d7689921f0daef5 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: fix slab-out-of-bounds write in wacom_wac_queue_insert wacom_wac_queue_insert() calls kfifo_skip() in a loop when the kfifo doesn't have enough space for the incoming report. If the kfifo is empty, kfifo_skip() reads stale data left in the kmalloc'd buffer via __kfifo_peek_n() and interprets it as a record length, advancing fifo->out by that garbage value. This corrupts the internal kfifo state, causing kfifo_unused() to return a value much larger than the actual buffer size, which bypasses __kfifo_in_r()'s guard: if (len + recsize > kfifo_unused(fifo)) return 0; kfifo_copy_in() then performs an out-of-bounds memcpy, writing up to 3842 bytes past the 256-byte buffer. Add a !kfifo_is_empty() condition to the while loop so kfifo_skip() is never called on an empty fifo, and check the return value of kfifo_in() to reject reports that are too large for the fifo.
Quoted source text, attributed separately from HOL analysis.