Answer in brief
CVE-2026-89826 records a Unknown severity vulnerability in drm/panthor: harden firmware build-info bounds checks. 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 | >=2718d91816eeed03c09c8abe872e45f59078768c <5516f1acfd07564361cf306cc90a8e513df0f096 || >=2718d91816eeed03c09c8abe872e45f59078768c <6ae19dce3e8c13ae73590b3f4311abe9f96bbae8 || >=2718d91816eeed03c09c8abe872e45f59078768c <8321b093fa6c297b80586460ce6914d9655df170 | 5516f1acfd07564361cf306cc90a8e513df0f096, 6ae19dce3e8c13ae73590b3f4311abe9f96bbae8, 8321b093fa6c297b80586460ce6914d9655df170 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: harden firmware build-info bounds checks panthor_fw_read_build_info() checks whether the metadata range fits in the firmware image with hdr.meta_start + hdr.meta_size. Both fields are u32, so the addition can wrap and let an out-of-bounds range pass validation. The function also reads the "git_sha: " prefix without first checking that the metadata is long enough, and meta_size == 0 can underflow the NULL terminator index. Use subtraction-based bounds checking and reject metadata that is too short to contain the expected prefix and trailing NULL byte.
Quoted source text, attributed separately from HOL analysis.