Bug 2495950 (CVE-2026-53356) - CVE-2026-53356 kernel: drm/i915/gem: Fix phys BO pread/pwrite with offset
Summary: CVE-2026-53356 kernel: drm/i915/gem: Fix phys BO pread/pwrite with offset
Keywords:
Status: NEW
Alias: CVE-2026-53356
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-01 14:03 UTC by OSIDB Bzimport
Modified: 2026-08-20 05:22 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:57251 0 None None None 2026-08-20 05:22:26 UTC
Red Hat Product Errata RHSA-2026:57252 0 None None None 2026-08-20 05:13:20 UTC

Description OSIDB Bzimport 2026-07-01 14:03:09 UTC 
In the Linux kernel, the following vulnerability has been resolved:

drm/i915/gem: Fix phys BO pread/pwrite with offset

sg_page() returns struct page pointer not (void *) so the scaling
of pread/pwrite is wrong for phys BO and wrong parts of BO would be
accessed if non-zero offset is used.

Last impacted platform with overlay or cursor planes using phys
mapping was Gen3/945G/Lakeport.

(cherry picked from commit 3e49a2f85070b2fb672c1e0fdba281a4ea3aebe6)
Comment 1 Mauro Matteo Cascella 2026-07-01 16:42:07 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026070147-CVE-2026-53356-0d5f@gregkh/T
Comment 3 errata-xmlrpc 2026-08-20 05:13:19 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:57252 https://access.redhat.com/errata/RHSA-2026:57252
Comment 4 errata-xmlrpc 2026-08-20 05:22:25 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:57251 https://access.redhat.com/errata/RHSA-2026:57251
Note You need to log in before you can comment on or make changes to this bug.