LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23051: drm/amdgpu: fix drm panic null pointer when driver not support atomic

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix drm panic null pointer when driver not support atomic When driver not support atomic, fb using plane->fb rather than plane->state->fb. (cherry picked from commit 2f2a72de673513247cd6fae14e53f6c40c5841ef)

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-23051 is a Linux kernel amdgpu graphics driver flaw that can trigger a kernel panic. In business terms, affected Linux systems using the AMDGPU DRM path could crash, causing availability impact. Public data does not show active exploitation or a CVSS score.

Executive priority

Treat as a targeted availability risk. Prioritize patching workstations, GPU-enabled Linux systems, and any critical systems using AMDGPU display paths. Broader emergency response is not supported by the current evidence.

Technical view

The fix changes amdgpu DRM framebuffer handling when atomic modesetting is unsupported. The vulnerable path used plane->state->fb where plane->fb should be used, creating a NULL pointer panic condition. The CVE record lists Linux kernel versions and stable commits, but exact affected range details are limited in the provided data.

Likely exposure

Exposure is most relevant to Linux systems using the amdgpu DRM driver, especially configurations where the driver does not support atomic modesetting. Servers without AMD GPU graphics exposure may be less relevant. Exact version boundaries should be confirmed against kernel vendor advisories.

Exploitation context

No source in the bundle reports active exploitation, and the CVE is not listed as KEV. The described impact is a kernel panic, suggesting denial of service rather than data theft or code execution based on available evidence.

Researcher notes

The public record lacks CVSS, CWE, exploitability details, and clear version range semantics. Analysis should focus on commit comparison and downstream distribution advisories. Avoid assuming remote reachability or privilege impact beyond the documented NULL pointer kernel panic.

Mitigation direction

  • Review kernel vendor guidance for CVE-2026-23051.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems using AMDGPU graphics or DRM display paths.
  • If updates are delayed, assess whether affected GPU functionality can be reduced.

Validation and detection

  • Inventory Linux systems with AMDGPU hardware and amdgpu driver usage.
  • Compare running kernel versions against vendor fixed releases.
  • Check whether the kernel includes the referenced stable commits.
  • Monitor logs for DRM or amdgpu panic indicators.
Prepared
Confidence
medium
Sources
4

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-23051 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
3Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfe151ed7af5425c424a5735ef9fa3d02c828be7f, fe151ed7af5425c424a5735ef9fa3d02c828be7funaffected
LinuxLinux6.14, 0, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

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