CVE-2026-53356

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 1, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 18, 2026
No patch confirmed yet.
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d21ad938398bca695a511307de38a65889e3b354
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dd51a2eeb93bc6faa892ff9083911dd23f82c187
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32d4c5d328a3ff995420f4f85163e1e403f43628
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bd168dd835b93a3862cd05b0d13c432b115f9d6
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07c33be968d9e0cab6cba38c81850a09942fcb2e
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14469860e2e39b7095dcd658d2bad38a11110a68
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ec8fc63e9cdb22da54e48e536c9204020416fc6
generic

drm/i915/gem: Fix phys BO pread/pwrite with offset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40f738991058eb3e3530c3006a5bd6fd5e29f035

Vendor Advisories for CVE-2026-53356(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)7.0.13-1—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 137× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 224 total refreshes for this CVE.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-27 22:27 UTCEG score recompute
  4. 2026-08-27 22:27 UTCVendor advisory
  5. 2026-08-27 22:27 UTCGHSA enrichment
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-24 23:23 UTCEG score recompute
  10. 2026-08-24 23:23 UTCVendor advisory
  11. 2026-08-24 23:23 UTCGHSA enrichment
  12. 2026-08-24 10:54 UTCEG score recompute
  13. 2026-08-24 10:54 UTCVendor advisory
  14. 2026-08-24 10:54 UTCGHSA enrichment
  15. 2026-08-23 21:02 UTCVendor advisory
  16. 2026-08-23 21:02 UTCGHSA enrichment
  17. 2026-08-23 08:32 UTCEG score recompute
  18. 2026-08-23 08:32 UTCVendor advisory
  19. 2026-08-23 08:32 UTCGHSA enrichment
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-22 20:03 UTCVendor advisory
  22. 2026-08-22 20:03 UTCGHSA enrichment
  23. 2026-08-22 07:21 UTCVendor advisory
  24. 2026-08-22 07:21 UTCGHSA enrichment
  25. 2026-08-21 18:13 UTCVendor advisory
Show 75 more
  1. 2026-08-21 18:13 UTCGHSA enrichment
  2. 2026-08-21 05:44 UTCEG score recompute
  3. 2026-08-21 05:44 UTCVendor advisory
  4. 2026-08-21 05:44 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 17:15 UTCVendor advisory
  7. 2026-08-20 17:15 UTCGHSA enrichment
  8. 2026-08-20 04:45 UTCEG score recompute
  9. 2026-08-20 04:45 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 09:55 UTCVendor advisory
  12. 2026-08-19 09:55 UTCGHSA enrichment
  13. 2026-08-18 21:00 UTCEG score recompute
  14. 2026-08-18 21:00 UTCVendor advisory
  15. 2026-08-18 21:00 UTCGHSA enrichment
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-18 04:50 UTCEG score recompute
  18. 2026-08-18 04:50 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 12:52 UTCVendor advisory
  21. 2026-08-17 12:52 UTCGHSA enrichment
  22. 2026-08-17 00:23 UTCEG score recompute
  23. 2026-08-17 00:23 UTCVendor advisory
  24. 2026-08-17 00:23 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
  26. 2026-08-16 11:53 UTCEG score recompute
  27. 2026-08-16 11:53 UTCVendor advisory
  28. 2026-08-16 11:53 UTCGHSA enrichment
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-15 23:25 UTCVendor advisory
  31. 2026-08-15 23:25 UTCGHSA enrichment
  32. 2026-08-15 10:56 UTCEG score recompute
  33. 2026-08-15 10:56 UTCVendor advisory
  34. 2026-08-15 10:56 UTCGHSA enrichment
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 22:26 UTCVendor advisory
  37. 2026-08-14 22:26 UTCGHSA enrichment
  38. 2026-08-14 09:57 UTCEG score recompute
  39. 2026-08-14 09:57 UTCGHSA enrichment
  40. 2026-08-13 22:00 UTCEPSS rescore
  41. 2026-08-13 21:28 UTCVendor advisory
  42. 2026-08-13 21:28 UTCGHSA enrichment
  43. 2026-08-13 08:53 UTCVendor advisory
  44. 2026-08-13 08:53 UTCGHSA enrichment
  45. 2026-08-12 20:25 UTCEG score recompute
  46. 2026-08-12 20:25 UTCVendor advisory
  47. 2026-08-12 20:25 UTCGHSA enrichment
  48. 2026-08-12 13:51 UTCEPSS rescore
  49. 2026-08-12 07:56 UTCVendor advisory
  50. 2026-08-12 07:56 UTCGHSA enrichment
  51. 2026-08-11 19:27 UTCEG score recompute
  52. 2026-08-11 19:27 UTCVendor advisory
  53. 2026-08-11 19:27 UTCGHSA enrichment
  54. 2026-08-11 06:59 UTCEG score recompute
  55. 2026-08-11 06:59 UTCVendor advisory
  56. 2026-08-11 06:59 UTCGHSA enrichment
  57. 2026-08-11 00:00 UTCEPSS rescore
  58. 2026-08-10 18:29 UTCGHSA enrichment
  59. 2026-08-10 05:55 UTCGHSA enrichment
  60. 2026-08-09 17:26 UTCEG score recompute
  61. 2026-08-09 17:26 UTCGHSA enrichment
  62. 2026-08-09 13:46 UTCEPSS rescore
  63. 2026-08-09 04:58 UTCEG score recompute
  64. 2026-08-09 04:58 UTCGHSA enrichment
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-08 16:29 UTCVendor advisory
  67. 2026-08-08 16:29 UTCGHSA enrichment
  68. 2026-08-08 03:59 UTCEG score recompute
  69. 2026-08-08 03:59 UTCGHSA enrichment
  70. 2026-08-07 15:30 UTCGHSA enrichment
  71. 2026-08-07 03:01 UTCVendor advisory
  72. 2026-08-07 03:01 UTCGHSA enrichment
  73. 2026-08-06 14:32 UTCEG score recompute
  74. 2026-08-06 14:32 UTCVendor advisory
  75. 2026-08-06 14:32 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53356?
CVE-2026-53356 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-53356 disclosed?
CVE-2026-53356 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53356 actively exploited?
CVE-2026-53356 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53356?
CVE-2026-53356 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53356?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53356, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53356

Explore →

Is Your Infrastructure Affected by CVE-2026-53356?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs