CVE-2026-53068

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

drm/komeda: fix integer overflow in AFBC framebuffer size check

The AFBC framebuffer size validation calculates the minimum required buffer size by adding the AFBC payload size to the framebuffer offset. This addition is performed without checking for integer overflow.

If the addition oveflows, the size check may incorrectly succed and allow userspace to provide an undersized drm_gem_object, potentially leading to out-of-bounds memory access.

Add usage of check_add_overflow() to safely compute the minimum required size and reject the framebuffer if an overflow is detected. This makes the AFBC size validation more robust against malformed.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

CVSS v3
7.1
EG Score
7.1(high)
EPSS
1.9%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/872d923b852705054bc099af663da862fdc1097d
generic

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8165e8b28fdf392c2c7412518d602b4f193812a8
generic

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/779ec12c85c9e4547519e3903a371a3b26a289de
generic

drm/komeda: fix integer overflow in AFBC framebuffer size check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02ff8a7d3d0eecc546b9ab4c07b3d7c65d485583

Vendor Advisories for CVE-2026-53068(2)

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

Data Freshness Timeline

(refreshed 39× in last 7d / 51× 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.

  1. 2026-07-07 06:56 UTCEG score recompute
  2. 2026-07-07 06:56 UTCGHSA enrichment
  3. 2026-07-06 19:50 UTCEG score recompute
  4. 2026-07-06 19:50 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 08:15 UTCEG score recompute
  8. 2026-07-06 08:15 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 21:09 UTCEG score recompute
  12. 2026-07-05 21:09 UTCGHSA enrichment
  13. 2026-07-05 10:03 UTCEG score recompute
  14. 2026-07-05 10:02 UTCGHSA enrichment
  15. 2026-07-05 02:31 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 22:56 UTCEG score recompute
  18. 2026-07-04 22:56 UTCGHSA enrichment
  19. 2026-07-04 11:51 UTCEG score recompute
  20. 2026-07-04 11:51 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 00:45 UTCEG score recompute
  23. 2026-07-04 00:45 UTCGHSA enrichment
  24. 2026-07-03 13:35 UTCEG score recompute
  25. 2026-07-03 13:35 UTCGHSA enrichment
Show 26 more
  1. 2026-07-03 02:31 UTCEG score recompute
  2. 2026-07-03 02:30 UTCGHSA enrichment
  3. 2026-07-02 15:26 UTCEG score recompute
  4. 2026-07-02 15:26 UTCGHSA enrichment
  5. 2026-07-02 04:21 UTCEG score recompute
  6. 2026-07-02 04:21 UTCGHSA enrichment
  7. 2026-07-01 17:16 UTCEG score recompute
  8. 2026-07-01 17:16 UTCGHSA enrichment
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-07-01 06:12 UTCEG score recompute
  11. 2026-07-01 06:12 UTCGHSA enrichment
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 19:06 UTCEG score recompute 7.10
  14. 2026-06-30 19:06 UTCGHSA enrichment
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 18:41 UTCEG score recompute
  22. 2026-06-27 18:41 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 18:15 UTCEG score recompute
  26. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53068?
CVE-2026-53068 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/komeda: fix integer overflow in AFBC framebuffer size check The AFBC framebuffer size validation calculates the minimum required buffer size by adding the AFBC payload size to the framebuffer offset. This addition is performed…
When was CVE-2026-53068 disclosed?
CVE-2026-53068 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53068 actively exploited?
CVE-2026-53068 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53068?
CVE-2026-53068 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53068?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53068, 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

Explore the affected products and dependency analysis for CVE-2026-53068

Explore →

Is Your Infrastructure Affected by CVE-2026-53068?

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