Answer in brief
CVE-2026-80572 records a Unknown severity vulnerability in Input: byd - synchronize timer deletion before freeing private data. 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2d5f5611dd0de52e9a52b56391a7049a52184e72 <8dbfd8e32a13e116790780ed0be82b5a05eb9916 || >=2d5f5611dd0de52e9a52b56391a7049a52184e72 <2e509ef60ee41a2da0deb062c262bb530143fb37 || >=2d5f5611dd0de52e9a52b56391a7049a52184e72 <c83e79c0842ed29860648bcce5022ef0ba5001c6 | 8dbfd8e32a13e116790780ed0be82b5a05eb9916, 2e509ef60ee41a2da0deb062c262bb530143fb37, c83e79c0842ed29860648bcce5022ef0ba5001c6 |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 26, 2026
In the Linux kernel, the following vulnerability has been resolved: Input: byd - synchronize timer deletion before freeing private data byd_disconnect() uses timer_delete() before freeing the driver's private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress. Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.
Quoted source text, attributed separately from HOL analysis.