[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026021413-CVE-2026-23149-8329@gregkh>
Date: Sat, 14 Feb 2026 17:04:15 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23149: drm: Do not allow userspace to trigger kernel warnings in drm_gem_change_handle_ioctl()
From: Greg Kroah-Hartman <gregkh@...nel.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.
The Linux kernel CVE team has assigned CVE-2026-23149 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 53096728b8910c6916ecc6c46a5abc5c678b58d9 and fixed in 6.18.9 with commit ae8831ee0fb2f5f41f39722e7b3749d65bb78d08
Issue introduced in 6.18 with commit 53096728b8910c6916ecc6c46a5abc5c678b58d9 and fixed in 6.19 with commit 12f15d52d38ac53f7c70ea3d4b3d76afed04e064
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-23149
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/drm_gem.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/ae8831ee0fb2f5f41f39722e7b3749d65bb78d08
https://git.kernel.org/stable/c/12f15d52d38ac53f7c70ea3d4b3d76afed04e064
Powered by blists - more mailing lists