VulnerabilityPublished 23 Oct 2026

CVE-2026-99004: Linux kernel · drm/imagination: Size page table preallocation by device address

Source GCVE Database

Authoritative record:CVE-2026-99004· High

Not known to be exploited · fixed in f9b215b3e37a5047c406545de51bf8a2aeb4cd1c : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f9b215b3e37a5047c406545de51bf8a2aeb4cd1c, 789f290b2e81d42820bddcb4010ffbc2ae2ded54, 51b56bad96fd20127034f660b337c00317c65151 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-862j-6x74-2p6m

What to do

Upgrade Linux kernel to f9b215b3e37a5047c406545de51bf8a2aeb4cd1c, 789f290b2e81d42820bddcb4010ffbc2ae2ded54, 51b56bad96fd20127034f660b337c00317c65151 or 7f73da0facf864fe796371ebaccacb1fee678aaf.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < f9b215b3e37a5047c406545de51bf8a2aeb4cd1c	Fixed in f9b215b3e37a5047c406545de51bf8a2aeb4cd1c
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 789f290b2e81d42820bddcb4010ffbc2ae2ded54	Fixed in 789f290b2e81d42820bddcb4010ffbc2ae2ded54
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 51b56bad96fd20127034f660b337c00317c65151	Fixed in 51b56bad96fd20127034f660b337c00317c65151
LinuxLinux	Affected ≥ ff5f643de0bf27874c4033cd57a0bd034b5c7d11, < 7f73da0facf864fe796371ebaccacb1fee678aaf	Fixed in 7f73da0facf864fe796371ebaccacb1fee678aaf
LinuxLinux	Affected =6.8	Fixed in–

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]

References

Community reviews

Loading reviews…