Kernel disclosure and crash via unchecked IB offsets
Published May 28, 2026 · Updated May 28, 2026
Out-of-bounds reads in Linux Kernel allow local users to disclose kernel memory or crash the system through crafted amdgpu command buffers. The UVD, VCE, and VCN parsing paths call ib_get_value at predefined indexes without first ensuring each index falls within the indirect buffer length; a signed index could also overflow the old comparison. Exploitation requires low-privileged access to the amdgpu render node and a supported AMD GPU; the defect provides read-only kernel-memory exposure and can trigger a kernel crash, but no write primitive is reported.
Summary
What happened
Out-of-bounds reads in Linux Kernel allow local users to disclose kernel memory or crash the system through crafted amdgpu command buffers. The UVD, VCE, and VCN parsing paths call ib_get_value at predefined indexes without first ensuring each index falls within the indirect buffer length; a signed index could also overflow the old comparison. Exploitation requires low-privileged access to the amdgpu render node and a supported AMD GPU; the defect provides read-only kernel-memory exposure and can trigger a kernel crash, but no write primitive is reported.
The record
- CVE
- CVE-2026-46218
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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.
- Affected versionversion=0 <6.12.90
- Affected versionversion=0 <6.18.32
- Affected versionversion=0 <6.6.140
- Affected versionversion=0 <7.0.9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0fb5cb556b249b2b64c0f818136c4c3e838ef53f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <66085e206431ef88ce36f53c1f53d570790ccc9e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a853178d23e774adfe3a35073c375b04b3b20f7d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee26fcf7c5cf131f0b6a732faa27d79ec61b8ec7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fec8b11b55e53ff51a741e56894fe331a516f5c6
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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