Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-53138: drm/amd/display: Bound VBIOS record-chain walk loops

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 04e271a952b8863bbafc99bd51aca4c32bff0e0d, 0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1, 2645e3caf7e013189da9c6ff621d006cca5a538b; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.144.1-1.

Low priority for now. Upgrade to Linux Linux 04e271a952b8863bbafc99bd51aca4c32bff0e0d, 0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1, 2645e3caf7e013189da9c6ff621d006cca5a538b; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.144.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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)

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Jul 7, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53138

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.15 and later · before 5.10.260
  • linux linux kernel5.11 and later · before 5.15.211
  • linux linux kernel5.16 and later · before 6.1.177
  • linux linux kernel6.2 and later · before 6.6.144
  • linux linux kernel6.7 and later · before 6.12.94
  • linux linux kernel6.13 and later · before 6.18.36
  • linux linux kernel6.19 and later · before 7.0.13
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.15affected
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before e94f5323c41f32a74160378c3b19850d1f203ad5affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 04e271a952b8863bbafc99bd51aca4c32bff0e0daffected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 6723188c42ca3b34a9fce634d7a0ecc9ccd5cd56affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 499c6b43a79dd684bddbd18fe8b2235aa2764db4affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 6173cfea2f916e01c4f98e29cd654384a05e32a3affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 2645e3caf7e013189da9c6ff621d006cca5a538baffected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before ff287df16a1a58aca78b08d1f3ee09fc44da0351affected · git
    • before 4.15not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.177-16.1.177-1
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.13-17.0.13-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53136Jun 25, 2026 · drm/amd/display: Clamp VBIOS HDMI retimer register count to array size
    31Monitor
  • ← EarlierCVE-2026-53137Jun 25, 2026 · drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size
    31Monitor
  • Later →CVE-2026-53139Jun 25, 2026 · drm/v3d: Skip CSD when it has zeroed workgroups
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux04e271a952b8863bbafc99bd51aca4c32bff0e0dVendor (CNA)
Linux Linux0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1Vendor (CNA)
Linux Linux2645e3caf7e013189da9c6ff621d006cca5a538bVendor (CNA)
Linux Linux499c6b43a79dd684bddbd18fe8b2235aa2764db4Vendor (CNA)
Linux Linux6173cfea2f916e01c4f98e29cd654384a05e32a3Vendor (CNA)
Linux Linux6723188c42ca3b34a9fce634d7a0ecc9ccd5cd56Vendor (CNA)
Linux Linuxe94f5323c41f32a74160378c3b19850d1f203ad5Vendor (CNA)
Linux Linuxff287df16a1a58aca78b08d1f3ee09fc44da0351Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.144.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.177-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records