Unspecified impact via DRM device registration race
Published Sep 16, 2026 · Updated Sep 16, 2026
Race condition in the DRM registration path in Linux allows local users to cause unspecified impact through an ioctl during failed setup. On a partial drm_dev_register() failure after one minor is registered, the error path tears down device resources without setting unplugged or waiting for drm_dev_enter() critical sections, so an in-flight ioctl continues against resources being removed. Reaching the race requires local access to an exposed DRM minor during a registration failure; the upstream disclosure does not define the resulting security consequence.
Summary
What happened
Race condition in the DRM registration path in Linux allows local users to cause unspecified impact through an ioctl during failed setup. On a partial drm_dev_register() failure after one minor is registered, the error path tears down device resources without setting unplugged or waiting for drm_dev_enter() critical sections, so an in-flight ioctl continues against resources being removed. Reaching the race requires local access to an exposed DRM minor during a registration failure; the upstream disclosure does not define the resulting security consequence.
The record
- CVE
- CVE-2026-89823
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- 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=4.18
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <19dbfe4d586aecfed121cb3fa62281761d9d341f
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <24d28d15c0f7f7d4a1c229f8730314f0f8758810
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <26d9162213952927cd59c0d94b7e0e992b347bec
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <2d1215a72159d00001e08dee162e27718934bee9
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <6729990df9e70623bf53f855b521ae71ca9cb278
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <79d09cfe90304ff4f195e47d569800f5e0f8b854
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <a0a7e2e177f2f18b9e7318a4c64ac44efd9ef22c
- Affected versionversion=bee330f3d67273a68dcb99f59480d59553c008b2 <eb197f7d60f00d0f5b1b3505dfc86a7e36045a3e
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
No sourced classifications are available.
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