drm/i915/gem: Fix Virtual Memory mapping boundaries calculation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c58305af1835095ddc25ee6f548ac05915e66ac5 · < 4b09513ce93b3dcb590baaaff2ce96f2d098312d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/gem: Fix Virtual Memory mapping boundaries calculation
Calculating the size of the mapped area as the lesser value between the requested size and the actual size does not consider the partial mapping offset. This can cause page fault access.
Fix the calculation of the starting and ending addresses, the total size is now deduced from the difference between the end and start addresses.
Additionally, the calculations have been rewritten in a clearer and more understandable form.
[Joonas: Add Requires: tag] Requires: 60a2066c5005 ("drm/i915/gem: Adjust vma offset for framebuffer mmap offset") (cherry picked from commit 97b6784753da06d9d40232328efc5c5367e53417)
From the CVE record · Linux
The Linux kernel’s drm/i915/gem code can calculate virtual memory mapping boundaries incorrectly when a partial mapping has an offset. Accessing the affected mapping can cause a page fault; the input does not specify authentication requirements or further impact.
Engineers running Linux kernels that include commit 60a2066c5005 should check whether their kernel has the fix; affected versions are not specified.