Answer in brief
CVE-2026-98566 records a Unknown severity vulnerability in drm/imagination: clamp freelist reconstruction requests. 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 | >=6eedddab733b350886571f98b810108b13bf74ae <b78f8f5532a077baa4aabccf657a4fb3b164659e || >=6eedddab733b350886571f98b810108b13bf74ae <e0560db0ea6e10c283ebe7c259a7af8d3b6e61a6 || >=6eedddab733b350886571f98b810108b13bf74ae <eabd0ae3611769c826dbc118a1e240628731b348 || >=6eedddab733b350886571f98b810108b13bf74ae <45585c3aa285854face65293acc95eff73063d6d | b78f8f5532a077baa4aabccf657a4fb3b164659e, e0560db0ea6e10c283ebe7c259a7af8d3b6e61a6, eabd0ae3611769c826dbc118a1e240628731b348, 45585c3aa285854face65293acc95eff73063d6d |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/imagination: clamp freelist reconstruction requests The firmware reconstruction count controls accesses to the request's fixed freelist ID array and the copy into the fixed response array. Neither access currently bounds the count to those protocol arrays. Clamp the count to the request capacity, which is shared by the response layout, and use that count consistently for reconstruction and response publication. Keep the firmware recovery exchange instead of dropping an oversized request without a response, as discussed with the firmware maintainer. The issue was found by our static-analysis tool.
Quoted source text, attributed separately from HOL analysis.