CVE-2026-53138

Memory disclosure via unbounded VBIOS parsing

Published Jun 25, 2026 · Updated Jun 25, 2026

Out-of-bounds read in the AMD display driver in Linux Kernel allows local users to disclose kernel memory via malformed VBIOS data. The 14 record-chain loops in bios_parser.c and bios_parser2.c stop only at a sentinel or zero size, then cast records beyond the two-byte header checked by GET_IMAGE. Exploitation requires local privileges and crafted AMD VBIOS data at device probe, allowing memory disclosure or prolonged probe iteration.

CVSS severity7.1
High
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds read in the AMD display driver in Linux Kernel allows local users to disclose kernel memory via malformed VBIOS data. The 14 record-chain loops in bios_parser.c and bios_parser2.c stop only at a sentinel or zero size, then cast records beyond the two-byte header checked by GET_IMAGE. Exploitation requires local privileges and crafted AMD VBIOS data at device probe, allowing memory disclosure or prolonged probe iteration.

The record

CVE
CVE-2026-53138
Published
Jun 25, 2026
Updated
Jun 25, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-125
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.15
  2. Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1
  3. Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <2645e3caf7e013189da9c6ff621d006cca5a538b
  4. Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <6173cfea2f916e01c4f98e29cd654384a05e32a3
  5. Affected versionversion=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <ff287df16a1a58aca78b08d1f3ee09fc44da0351

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=4.15; version=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <0e56f460bddb397fa9a8e6faf7ae7eaa86953eb1; version=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <2645e3caf7e013189da9c6ff621d006cca5a538b; version=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <6173cfea2f916e01c4f98e29cd654384a05e32a3; version=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <ff287df16a1a58aca78b08d1f3ee09fc44da0351

Published CVSS scores

5.1Amazon LinuxCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H
7.1NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-125Out-of-bounds Read

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo