CVE-2026-53138

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
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.1Exploit: None knownExposed: 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/amd/display: Bound VBIOS record-chain walk loops

[Why & How] All record-chain walk loops in bios_parser.c and bios_parser2.c use for(;;) and only terminate on a 0xFF record_type sentinel or zero record_size. A malformed VBIOS image missing the terminator record causes unbounded iteration at probe time, potentially hundreds of thousands of iterations with record_size=1. In the final iterations near the BIOS image boundary, struct casts beyond the 2-byte header validated by GET_IMAGE can also read out of bounds.

Cap all 14 record-chain walk loops to BIOS_MAX_NUM_RECORD (256) iterations. The atombios.h defines up to 22 distinct record types and atomfirmware.h has 13. Assuming an average of less than 10 records per type (which is reasonable since most are connector- based) 256 is a generous upper bound.

(cherry picked from commit 95700a3d660287ed657d6892f7be9ffc0e294a93)

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (8)

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

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6723188c42ca3b34a9fce634d7a0ecc9ccd5cd56
generic

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6173cfea2f916e01c4f98e29cd654384a05e32a3
generic

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/499c6b43a79dd684bddbd18fe8b2235aa2764db4
generic

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2645e3caf7e013189da9c6ff621d006cca5a538b
generic

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1
generic

drm/amd/display: Bound VBIOS record-chain walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04e271a952b8863bbafc99bd51aca4c32bff0e0d

Vendor Advisories for CVE-2026-53138(2)

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

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-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 (145 versions)7.0.13-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 83× 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 248 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53138?
CVE-2026-53138 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Bound VBIOS record-chain walk loops [Why & How] All record-chain walk loops in biosparser.c and biosparser2.c use for(;;) and only terminate on a 0xFF record_type sentinel or zero record_size. A malformed VBIOS…
When was CVE-2026-53138 disclosed?
CVE-2026-53138 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53138 actively exploited?
CVE-2026-53138 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-53138?
CVE-2026-53138 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53138?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53138, 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-53138

Explore →

Is Your Infrastructure Affected by CVE-2026-53138?

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

Start Free Scan →Browse All CVEs