CVE-2026-99004

drm/imagination: Size page table preallocation by device address

State
Published
Severity
Not scored
Published
Oct 23, 2026
Updated
Oct 23, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

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]

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • ff5f643de0bf27874c4033cd57a0bd034b5c7d11 to before 51b56bad96fd20127034f660b337c00317c65151Affected
  • ff5f643de0bf27874c4033cd57a0bd034b5c7d11 to before f9b215b3e37a5047c406545de51bf8a2aeb4cd1cAffected
  • ff5f643de0bf27874c4033cd57a0bd034b5c7d11 to before 7f73da0facf864fe796371ebaccacb1fee678aafAffected
  • ff5f643de0bf27874c4033cd57a0bd034b5c7d11 to before 789f290b2e81d42820bddcb4010ffbc2ae2ded54Affected
LinuxLinux
  • 6.8Affected
  • before 6.8Not affected
  • 6.12.113 through 6.12.*Not affected
  • 6.18.57 through 6.18.*Not affected
  • 7.2.11 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.