[CVE-2026-53313][LOW] drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths [ Upstream

[CVE-2026-53313][LOW] drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths [ Upstream

[AL-KERNEL]

CVE: CVE-2026-53313
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths [ Upstream
Commit: b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53313
Analysis date: Fri, 26 Jun 2026 16:52:43 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A NULL pointer dereference in AMD display DMUB error handling can occur when logging uses dc_dmub_srv ctx after dc_dmub_srv is NULL, potentially causing a local device-specific kernel crash without evidence of privilege escalation.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53313 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53313

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-53313	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A NULL-pointer dereference can occur in AMD display DMUB error paths because DC_LOG_ERROR may use dc_dmub_srv ctx even when dc_dmub_srv is NULL. A local user or local process may be able to reach the affected display driver paths only under specific device or error state conditions, so reliability is expected to be low. For the CVSS the PR:L is used because a local user context is the most defensible paranoid interpretation, while full administrative privileges are not clearly required by the patch context. The issue is not network reachable. Impact is denial of service through a possible kernel crash, with no supported evidence of information disclosure or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-53313  SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	DANGER NULLPTR ERRORPATH HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

* Weak corruption or invalid pointer dereference: +0
  The bug is a NULL pointer dereference through `DC_LOG_ERROR()` when `dc_dmub_srv` is NULL. This is not UAF, double-free, OOB write, arbitrary write, or object lifetime corruption.

* Local unprivileged trigger, paranoid only: +1
  A local user or process may indirectly reach display driver paths through normal graphics/display activity, but the specific DMUB error paths are not shown to be directly controllable.

* Availability impact realistic: +1
  If the affected error path is reached with `dc_dmub_srv == NULL`, the kernel may crash.

* Rare and difficult-to-reach condition: -1
  The vulnerable path depends on AMD display DMUB-specific error handling and a NULL service object state. It is not a common syscall, networking, filesystem, or broadly reachable data-plane path.

* Broad/default/common subsystem, paranoid only: +1
  AMD display drivers are common on systems with AMD GPUs, but the vulnerable condition itself is still narrow.

## 3. Reachability analysis

The issue is local and device-specific. It is not network reachable and has no firmware-mediated remote trigger shown by the patch. A local user may be able to exercise graphics/display paths, but the crash requires a specific internal error state where `dc_dmub_srv` is NULL and the diagnostic or DPIA trace path is invoked. Namespaces and containers do not materially improve reachability unless the container has direct DRM device access. The path is relevant only on systems using the AMD display stack with the affected DMUB code.

## 4. Severity interpretation

This behaves like an ordinary Low/Moderate denial-of-service issue, not an Important-class vulnerability. The theoretical impact is a kernel crash from a NULL dereference. There is no evidence of memory corruption, attacker-controlled overwrite, UAF reclaim, information disclosure, credential exposure, or privilege escalation. The realistic exploitability is limited by the need to hit a narrow AMD display error path.

## 5. One-sentence report phrase

A NULL pointer dereference in AMD display DMUB error handling can occur when logging uses dc_dmub_srv ctx after dc_dmub_srv is NULL, potentially causing a local device-specific kernel crash without evidence of privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

The issue is a constrained NULL dereference in a driver error path, with no demonstrated memory corruption or security-boundary bypass. It can be handled as ordinary Moderate or Low-like unless a separate reproducer shows reliable unprivileged triggering.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths [ Upstream
Commit: b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22

Changed files:
  drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53313 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53313

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 1
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).