LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23366: drm/client: Do not destroy NULL modes

In the Linux kernel, the following vulnerability has been resolved: drm/client: Do not destroy NULL modes 'modes' in drm_client_modeset_probe may fail to kcalloc. If this occurs, we jump to 'out', calling modes_destroy on it, which dereferences it. This may result in a NULL pointer dereference in the error case. Prevent that.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can crash a vulnerable system path when memory allocation fails in DRM client display handling. The public record describes a NULL pointer dereference, which is mainly an availability concern. There is no source evidence of active exploitation or data theft.

Executive priority

Treat this as a normal-priority kernel maintenance item unless affected systems are operationally critical. There is no cited active exploitation, but kernel availability bugs can still cause business disruption.

Technical view

drm_client_modeset_probe may fail to allocate modes with kcalloc, jump to cleanup, and call modes_destroy on a NULL pointer. The fix prevents destroying NULL modes. The source bundle provides stable kernel commit references but no CVSS, CWE, attacker prerequisites, or exploitability details.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions that include the vulnerable DRM client code. The source bundle lists Linux as affected and references stable fixes, but it does not define distributions, configurations, or required access conditions.

Exploitation context

CISA KEV status is false, and the supplied sources do not report active exploitation. Public evidence supports a kernel NULL dereference in an error path, not a confirmed remote compromise technique.

Researcher notes

The record lacks CVSS, CWE, detailed affected configuration data, and trigger conditions. Analysis should stay tied to kernel version lineage and vendor backports, because distribution kernels may carry fixes without matching upstream version numbers.

Mitigation direction

  • Track vendor kernel advisories for CVE-2026-23366.
  • Upgrade to a kernel build containing the referenced stable fixes.
  • Prioritize systems where display availability impacts operations.
  • Use distribution-provided kernel packages rather than manual patch assumptions.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and appliances.
  • Check whether running kernels include the referenced stable fix commits.
  • Review vendor advisories for affected distribution package versions.
  • Confirm patched systems boot and graphics workloads remain stable.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2026-23366 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3039cc0c0653c6e15130a8719c3237329a954670, 3039cc0c0653c6e15130a8719c3237329a954670, 3039cc0c0653c6e15130a8719c3237329a954670unaffected
LinuxLinux6.16, 0, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.