Security readout for executives and security teams
Plain-English summary
CVE-2026-23149 lets local userspace trigger Linux kernel warnings through a DRM/GEM handle-change ioctl. The public record describes a fix that rejects oversized handles. No active exploitation is reported in the provided sources, and no CVSS score is available.
Executive priority
Handle through normal kernel patch management, with higher priority for multi-user, desktop, GPU, or container hosts where untrusted local workloads may access DRM. Current evidence does not support emergency response.
Technical view
DRM GEM handles are u32 in the userspace API, while the internal idr_alloc() path uses int ranges. A handle value above INT_MAX can reach idr_alloc() and trigger WARN_ON_ONCE for a negative start value. The fix rejects handles above INT_MAX and clarifies limit calculation in int domain.
Likely exposure
Likely limited to systems running affected Linux kernel versions with DRM/GEM functionality reachable by local userspace. The provided affected data lists Linux 6.18 through before 6.18.9 and 6.19 as affected, but distribution backport status must be checked separately.
Exploitation context
The described trigger is local userspace input to a DRM ioctl. The sources do not indicate remote exploitation, privilege escalation, memory corruption, public exploit code, or KEV-listed active exploitation.
Researcher notes
Impact evidence is narrow: userspace can trigger a kernel warning via an oversized GEM handle. The CVE lacks CVSS, CWE, and exploitation evidence. Validate exact affected ranges against upstream stable commits and downstream vendor backports.
Mitigation direction
- Update to a vendor kernel containing the referenced DRM fix.
- Check Linux distribution advisories for backported fixed packages.
- Prioritize systems where untrusted local users or workloads access DRM devices.
Validation and detection
- Inventory running kernel versions on Linux systems.
- Confirm whether vendor kernel changelogs include the referenced DRM/GEM fix.
- Review exposure of DRM device access for untrusted local users or containers.
- Check logs for repeated DRM-related kernel warnings, without treating logs as proof of compromise.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2026-23149 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/ae8831ee0fb2f5f41f39722e7b3749d65bb78d08CVE reference, Linux
- https://git.kernel.org/stable/c/12f15d52d38ac53f7c70ea3d4b3d76afed04e064CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.