[CVE-2026-46245][LOW] drm/amd/display: Fix dc_link NULL handling in HPD init [ Upstream

[CVE-2026-46245][LOW] drm/amd/display: Fix dc_link NULL handling in HPD init [ Upstream

[AL-KERNEL]

CVE: CVE-2026-46245
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: drm/amd/display: Fix dc_link NULL handling in HPD init [ Upstream
Commit: a490e4d3c9fed1e690c8de348416eea3a9f054ff
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a490e4d3c9fed1e690c8de348416eea3a9f054ff
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46245
Analysis date: Sat, 01 Aug 2026 09:37:54 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A NULL pointer dereference in AMDGPU display HPD initialization can crash the kernel when a connector lacks a valid dc_link, but exploitation appears local, configuration dependent, and limited to denial of service.

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

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

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-46245	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	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:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A NULL-pointer dereference in the AMDGPU display HPD initialization path can occur because amdgpu_dm_hpd_init() can see a connector without a valid dc_link and later dereference dc_link during HPD IRQ setup. This can crash the kernel during driver initialization or display reinitialization on affected hardware or firmware configurations. For the CVSS the PR:L is used in the paranoid score because a local user may be able to indirectly trigger display reinit or GPU recovery in some desktop environments, while reliable triggering usually needs administrative control over driver load or reset. The issue is not network reachable and requires local interaction with the affected graphics stack or a matching hardware state. Impact is denial of service via kernel crash only. There is no evidence of UAF, OOB access, arbitrary write, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) 	MAYBE	WARNONLY LOG HARDWARE 	-	-	checked

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

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

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

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The patch prevents a direct NULL pointer dereference of `dc_link` in `amdgpu_dm_hpd_init()`.
* Requires admin/root/CAP_* in typical deployments: -2. Reliable triggering is likely tied to driver initialization, GPU reset, display reinitialization, suspend/resume, or affected hardware probing paths.
* Rare AND difficult-to-reach subsystem/configuration: -1. The crash requires an AMDGPU display connector object without a valid `dc_link`, which appears configuration or hardware-state dependent rather than a generally reachable userspace path.

Conservative total is floored to 0.

Paranoid signals:

* Local unprivileged trigger: +1. In some desktop environments, a local user may indirectly influence display hotplug, GPU recovery, or display reinitialization behavior.
* Reliable kernel crash / strong DoS: +1. If the affected state is reached, the unchecked dereference can crash the kernel.
* No memory corruption signal. This is a NULL dereference, not UAF, OOB write, type confusion, arbitrary write, or refcount corruption.
* No LPE signal. There is no reclaim, stale object reuse, callback control, write primitive, or attacker-controlled replacement.

Paranoid total: 2.

## 3. Reachability analysis

The bug is reachable in the AMDGPU display HPD initialization path when a DRM connector exists without a valid `dc_link`. In typical deployments, reliable triggering probably requires administrative control over driver load, reset, suspend/resume, GPU recovery, or a specific hardware/firmware display topology. A local unprivileged user may have some indirect influence in graphical desktop sessions through display hotplug or GPU recovery behavior, but the patch does not show a direct unprivileged userspace API that reliably creates the invalid state.

Namespaces and containers do not materially lower privileges for this path unless the container has direct GPU device access and can trigger display reinitialization. The path is not network reachable. The affected subsystem is common on AMDGPU systems, but the vulnerable condition is hardware or state dependent.

Call-site confidence: high, because the relevant function body and dereference site are present in the patch context.

## 4. Severity interpretation

This behaves like an ordinary Moderate or Low-like kernel DoS issue. The theoretical impact is a kernel crash through NULL pointer dereference. Realistic exploitation evidence is limited because no memory corruption primitive, privilege escalation path, confidentiality impact, or integrity impact is shown. The issue should not be treated as an Important candidate based on the provided patch.

## 5. One-sentence report phrase

A NULL pointer dereference in AMDGPU display HPD initialization can crash the kernel when a connector lacks a valid dc_link, but exploitation appears local, configuration dependent, and limited to denial of service.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: the patch shows a straightforward NULL dereference DoS with no UAF, OOB access, arbitrary write, object lifetime corruption, information disclosure, or plausible privilege escalation primitive.

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

Patch: drm/amd/display: Fix dc_link NULL handling in HPD init [ Upstream
Commit: a490e4d3c9fed1e690c8de348416eea3a9f054ff
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a490e4d3c9fed1e690c8de348416eea3a9f054ff

Changed files:
  drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_irq.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=a490e4d3c9fed1e690c8de348416eea3a9f054ff

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

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

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:H/UI:N/S:U/C:N/I:N/A:H
  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: 0
  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).