VulnerabilityPublished 14 Feb 2026Updated 5 Nov 2026

CVE-2026-23149: Linux kernel · drm: Do not allow userspace to trigger kernel warnings in drm_gem_change_handle_ioctl()

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to ae8831ee0fb2f5f41f39722e7b3749d65bb78d08 or 12f15d52d38ac53f7c70ea3d4b3d76afed04e064 when convenient.

Data as of 5 Nov 2026, 23:24 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

EPSS

0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in ae8831ee0fb2f5f41f39722e7b3749d65bb78d08, 12f15d52d38ac53f7c70ea3d4b3d76afed04e064

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to ae8831ee0fb2f5f41f39722e7b3749d65bb78d08 or 12f15d52d38ac53f7c70ea3d4b3d76afed04e064.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 53096728b8910c6916ecc6c46a5abc5c678b58d9, < ae8831ee0fb2f5f41f39722e7b3749d65bb78d08	Fixed in ae8831ee0fb2f5f41f39722e7b3749d65bb78d08
LinuxLinux	Affected ≥ 53096728b8910c6916ecc6c46a5abc5c678b58d9, < 12f15d52d38ac53f7c70ea3d4b3d76afed04e064	Fixed in 12f15d52d38ac53f7c70ea3d4b3d76afed04e064
LinuxLinux	Affected =6.18	Fixed in–

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.

References

Community reviews

Loading reviews…