Skip to main content

Linux Kernel CVE-2026-53356

| EUVDEUVD-2026-40990 HIGH
2026-07-01 Linux GHSA-v877-m38r-6c5w
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Local DRM device access needed so AV:L/PR:L; simple ioctl with non-zero offset triggers it (AC:L); OOB kernel read and write give C:H/I:H, and memory corruption can panic the kernel (A:H).

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
4.4 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 18, 2026 - 08:24 vuln.today
CVSS changed
Jul 18, 2026 - 08:22 NVD
7.8 (HIGH)
Patch available
Jul 01, 2026 - 15:16 EUVD
CVE Published
Jul 01, 2026 - 13:32 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 01, 2026 - 13:32 cve.org
HIGH 7.8

DescriptionCVE.org

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)

AnalysisAI

Out-of-bounds memory access in the Linux kernel's i915 (Intel graphics) DRM/GEM driver lets a local user with DRM device access read or corrupt kernel memory via pread/pwrite operations on physically-mapped buffer objects when a non-zero offset is supplied. The root cause is a pointer-scaling error where sg_page() returns a struct page pointer that was incorrectly treated as a byte pointer, so the offset arithmetic addresses the wrong memory. Rated CVSS 7.8 (local); EPSS is very low at 0.16% (6th percentile) and there is no public exploit identified at time of analysis, though a vendor patch is available.

Technical ContextAI

The flaw lives in the i915 GEM (Graphics Execution Manager) subsystem that manages GPU buffer objects (BOs). For 'phys' BOs - buffers backed by physically-contiguous system memory rather than the GTT - the driver serviced pread/pwrite ioctls by computing an address from the scatter-gather list. The code called sg_page(), which returns a 'struct page *', but scaled it as though it were a raw byte pointer (void *), so applying a user-supplied offset landed on the wrong memory region. Phys mapping was used for overlay and cursor planes; per the commit, the last impacted hardware was Intel Gen3 (945G / Lakeport-era) chipsets. No CWE was assigned in the input, but the defect is a classic incorrect pointer scaling / out-of-bounds read-write (in the CWE-787/CWE-125 family), driven by conflating page-granular and byte-granular pointer arithmetic.

RemediationAI

Vendor-released patch: upgrade to the fixed version for your stable series - 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13, or 7.1 (or later), applying the cherry-picked commit 3e49a2f85070b2fb672c1e0fdba281a4ea3aebe6 which corrects the sg_page() pointer scaling for phys BO pread/pwrite. The individual stable commits are available at https://git.kernel.org/stable/c/ (e.g. .../40f738991058eb3e3530c3006a5bd6fd5e29f035 and the sibling hashes in the reference set); take whichever your distribution ships and rebuild or install the updated kernel package. Since the fix is straightforward and released, patching is preferred over mitigation. If you cannot patch immediately, the compensating control is to restrict access to the DRM render/graphics devices (/dev/dri/*) to trusted users only and, on affected legacy hardware, avoid exposing multi-user local sessions - the trade-off is that limiting DRM access can break local graphical or GPU-compute functionality for non-privileged users, and this only matters on the rare Gen3/945G systems that use phys mapping.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected
Image SLES15-SP7-BYOS-Azure Image SLES15-SP7-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-Aliyun Image SLES15-SP7-CHOST-BYOS-Azure Image SLES15-SP7-CHOST-BYOS-EC2 Image SLES15-SP7-CHOST-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-GDC Image SLES15-SP7-CHOST-BYOS-SAP-CCloud Image SLES15-SP7-EC2 Image SLES15-SP7-EC2-ECS-HVM Image SLES15-SP7-GCE Image SLES15-SP7-HPC-BYOS-Azure Image SLES15-SP7-HPC-BYOS-EC2 Image SLES15-SP7-HPC-BYOS-GCE Image SLES15-SP7-Hardened-BYOS-Azure Image SLES15-SP7-Hardened-BYOS-EC2 Image SLES15-SP7-Hardened-BYOS-GCE Image SLES15-SP7-SAPCAL-Azure Image SLES15-SP7-SAPCAL-EC2 Image SLES15-SP7-SAPCAL-GCE Affected
Image SLES15-SP7-SAP-Azure Image SLES15-SP7-SAP-Azure-3P Image SLES15-SP7-SAP-BYOS-Azure Image SLES15-SP7-SAP-BYOS-EC2 Image SLES15-SP7-SAP-BYOS-GCE Image SLES15-SP7-SAP-EC2 Image SLES15-SP7-SAP-GCE Image SLES15-SP7-SAP-Hardened-Azure Image SLES15-SP7-SAP-Hardened-BYOS-Azure Image SLES15-SP7-SAP-Hardened-BYOS-EC2 Image SLES15-SP7-SAP-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Hardened-GCE Affected
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed

Share

CVE-2026-53356 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy