drm/imagination: Size page table preallocation by device address
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.113, 6.18.57, 7.2.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From ff5f643de0bf27874c4033cd57a0bd034b5c7d11 · fixed in 51b56bad96fd20127034f660b337c00317c65151; From ff5f643de0bf27874c4033cd57a0bd034b5c7d11 · fixed in f9b215b3e37a5047c406545de51bf8a2aeb4cd1c; From ff5f643de0bf27874c4033cd57a0bd034b5c7d11 · fixed in 7f73da0facf864fe796371ebaccacb1fee678aaf; From ff5f643de0bf27874c4033cd57a0bd034b5c7d11 · fixed in 789f290b2e81d42820bddcb4010ffbc2ae2ded54
- Linux Linux
6.8
- KernelLinux
From 6.8.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11