CVE-2026-80704: drm/amd/display: use proper context for logging
drm/amd/display: use proper context for logging
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 6f16fcbb0c46a87e3d9685407e906573d60104b0
Event History
Frequently Asked Questions
When can this NULL pointer dereference occur?
It can occur during AMD display clock-source construction, when get_ss_info_from_atombios() emits logging through DC_LOG_SYNC() before calc_pll_cs->ctx has been initialized. The same initialization-order issue is identified in dce112_get_pix_clk_dividers() and dcn3_get_pix_clk_dividers().
What configuration or hardware path is implicated?
The affected code is in the Linux kernel AMD display driver clock-source paths, including construction paths initialized by dce110_clk_src_construct() and dce112_clk_src_construct(). The issue is triggered by logging from the affected functions during that construction sequence.
What does the fix change?
The fix makes logging use clk_src->base.ctx->logger rather than calc_pll_cs->ctx->logger. The base context is initialized earlier, before the affected firmware-information and pixel-clock-divider functions are called.