CVE-2026-99004drm/imagination: Size page table preallocation by device address
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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]
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected ff5f643de0bf27874c4033cd57a0bd034b5c7d11 – < 51b56bad96fd20127034f660b337c00317c65151
- affected ff5f643de0bf27874c4033cd57a0bd034b5c7d11 – < f9b215b3e37a5047c406545de51bf8a2aeb4cd1c
- affected ff5f643de0bf27874c4033cd57a0bd034b5c7d11 – < 7f73da0facf864fe796371ebaccacb1fee678aaf
- affected ff5f643de0bf27874c4033cd57a0bd034b5c7d11 – < 789f290b2e81d42820bddcb4010ffbc2ae2ded54
- affected 6.8
- unaffected < 6.8
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.11 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/51b56bad96fd20127034f660b337c00317c65151 (opens in a new tab)
- https://git.kernel.org/stable/c/f9b215b3e37a5047c406545de51bf8a2aeb4cd1c (opens in a new tab)
- https://git.kernel.org/stable/c/7f73da0facf864fe796371ebaccacb1fee678aaf (opens in a new tab)
- https://git.kernel.org/stable/c/789f290b2e81d42820bddcb4010ffbc2ae2ded54 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108798 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99004)Record last updated .