Kernel crash via single-entry display LUT
Published Sep 16, 2026 · Updated Sep 16, 2026
Divide-by-zero in Linux allows attackers to crash the kernel via a single-entry AMD display color LUT passed to the AMDGPU driver. The __is_lut_linear() function divides an expected LUT value by size minus one without first rejecting a one-entry table, producing a processor divide error. Reachability requires the AMD display path and a single-entry LUT; successful triggering interrupts the host rather than disclosing or modifying data.
Summary
What happened
Divide-by-zero in Linux allows attackers to crash the kernel via a single-entry AMD display color LUT passed to the AMDGPU driver. The __is_lut_linear() function divides an expected LUT value by size minus one without first rejecting a one-entry table, producing a processor divide error. Reachability requires the AMD display path and a single-entry LUT; successful triggering interrupts the host rather than disclosing or modifying data.
The record
- CVE
- CVE-2026-89821
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=086247a4b2fba49800b27807f22bb894cd8363fb <15ee43aad0df43dfd1dbb32e7d5b951745c4b87f
- Affected versionversion=086247a4b2fba49800b27807f22bb894cd8363fb <2320626425f3af3a25b8afb6876f205b1c6d4e64
- Affected versionversion=086247a4b2fba49800b27807f22bb894cd8363fb <4d5ee095a58461b2446d7a6eb0c14c2fe3eaab44
- Affected versionversion=086247a4b2fba49800b27807f22bb894cd8363fb <4f40873f8a4107df2b9c8e68c947c4fd0cd519d2
- Affected versionversion=086247a4b2fba49800b27807f22bb894cd8363fb <5f18cd1ba873e751bf5547407ad44ea34adfbe2f
- Affected versionversion=086247a4b2fba49800b27807f22bb894cd8363fb <c127ace7af2b40107947a6504391f94d6fd21734
- Affected versionversion=086247a4b2fba49800b27807f22bb894cd8363fb <d1e06d5dc8f12451ce71dc068342660a34476084
- Affected versionversion=086247a4b2fba49800b27807f22bb894cd8363fb <ee28fafb50f58b847509b5240b431ddec673bdfe
- Affected versionversion=4.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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