Linux KernelOperating system · Linux
CVE-2026-53356
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn the Intel i915 GPU driver (drm/i915/gem), the sg_page() function returns a struct page pointer, but the code was incorrectly treating it as a void* for offset calculations in pread/pwrite operations. This type mismatch causes incorrect memory region access when physical buffer objects use non-zero offsets, potentially reading/writing to wrong parts of the buffer object.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 5.7, < 5.10.259>= 5.11, < 5.15.210>= 5.16, < 6.1.176>= 6.2, < 6.6.143>= 6.7, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if i915 GPU driver is loadedRun 'lsmod | grep i915' or check 'lspci -k | grep -A3 i915'Affected if i915 driver is not loaded means not affected; if loaded, continue to next checks
-
Determine kernel versionRun 'uname -r' to get the running kernel version and compare against versions containing the fixAffected if Kernel version predates the fix commit 3e49a2f85070b2fb672c1e0fdba281a4ea3aebe6
-
Identify GPU hardware generationRun 'lspci | grep -i vga' or check /sys/bus/pci/devices/*/driver for i915 bound devices; examine output for 945G, GMA 945, or Lakeport identifiersAffected if Hardware is legacy Gen3/945G/Lakeport chipset; modern systems with Gen4+ GPU are not affected by this specific flaw
-
Check for phys BO pread/pwrite usageThis requires code audit or tracing of i915 gem ioctl calls; look for applications using I915_GEM_PREAD or I915_GEM_PWRITE with a non-zero offset on physical buffer objectsAffected if Non-zero offset is used with phys BO pread/pwrite operations, triggering the incorrect memory offset calculation
System is affected only if running a vulnerable kernel on legacy Gen3/945G/Lakeport hardware while using phys BO pread/pwrite with a non-zero offset.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.10.2595.15.2106.1.176
Apply the kernel patch that corrects the type cast in the i915 gem driver. For systems using affected Gen3/945G/Lakeport hardware, ensure the kernel is updated to a version containing this fix.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53356 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data