CVE-2026-23149
Unknown Unknown - Not Provided
Integer Overflow in Linux DRM GEM Handle Allows Kernel Warnings

Publication date: 2026-02-14

Last updated on: 2026-03-17

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: drm: Do not allow userspace to trigger kernel warnings in drm_gem_change_handle_ioctl() Since GEM bo handles are u32 in the uapi and the internal implementation uses idr_alloc() which uses int ranges, passing a new handle larger than INT_MAX trivially triggers a kernel warning: idr_alloc(): ... if (WARN_ON_ONCE(start < 0)) return -EINVAL; ... Fix it by rejecting new handles above INT_MAX and at the same time make the end limit calculation more obvious by moving into int domain.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-14
Last Modified
2026-03-17
Generated
2026-06-16
AI Q&A
2026-02-14
EPSS Evaluated
2026-06-14
NVD
CVE-2026-23149
EUVD
EUVD-2026-5890
Affected Vendors & Products
Showing 8 associated CPEs
Vendor Product Version / Range
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel From 6.18 (inc) to 6.18.9 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically in the drm_gem_change_handle_ioctl() function. The issue arises because GEM buffer object handles are represented as 32-bit unsigned integers (u32) in the user API, but internally the kernel uses idr_alloc() which operates within signed integer (int) ranges.

If a user passes a new handle value larger than INT_MAX (the maximum value for a signed int), it triggers a kernel warning due to the internal idr_alloc() function checking for negative values and issuing a warning when the start value is less than zero.

The fix involves rejecting any new handles above INT_MAX and adjusting the internal calculations to stay within the int domain, preventing these kernel warnings from being triggered by userspace.

Impact Analysis

This vulnerability can cause kernel warnings to be triggered by userspace applications when they pass handle values larger than INT_MAX. While the description does not explicitly mention crashes or privilege escalation, kernel warnings can indicate instability or unexpected behavior in the kernel.

Such warnings may lead to degraded system reliability or potential denial of service if the kernel reacts adversely to these warnings. It could also complicate debugging and system monitoring due to unexpected kernel messages.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-23149. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart