Answer in brief
CVE-2026-99004 records a Unknown severity vulnerability in drm/imagination: Size page table preallocation by device address. 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 | >=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <51b56bad96fd20127034f660b337c00317c65151 || >=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <f9b215b3e37a5047c406545de51bf8a2aeb4cd1c || >=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <7f73da0facf864fe796371ebaccacb1fee678aaf || >=ff5f643de0bf27874c4033cd57a0bd034b5c7d11 <789f290b2e81d42820bddcb4010ffbc2ae2ded54 | 51b56bad96fd20127034f660b337c00317c65151, f9b215b3e37a5047c406545de51bf8a2aeb4cd1c, 7f73da0facf864fe796371ebaccacb1fee678aaf, 789f290b2e81d42820bddcb4010ffbc2ae2ded54 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Size page table preallocation by device address Commit 0a8224058a58 ("drm/imagination: Fix page count for page table for map() interface") passed the device address to pvr_mmu_op_context_create(), but the preallocation is still sized from device_addr + sgt_offset with an exclusive end. The offset into the object's pages has no place in a device-virtual range, and the exclusive end allocates one table too many when the range ends on a table boundary. Count the tables from device_addr and the inclusive end of the range. The new calculation does not take page table indices into account. This fixes another issue with the previous implementation, where the difference between start and end indices could underflow when a mapping crossed a page table boundary. This would lead to the driver preallocating a huge number of MMU pages, exhausting system memory and triggering an out of memory panic. [Alessio: add paragraph to point out OOM bug being fixed, cc stable]
Quoted source text, attributed separately from HOL analysis.