CVE-2026-80704drm/amd/display: use proper context for logging
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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)
Timeline
ID reserved
By Linux
- 2 days later
· 2 days later
Published
- 54 days later
· 54 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1296423bf23c7a58133970e223b1f47ec6570308 – < 07b52a41765722ec971e0cd9739b140bf4933998
- affected 1296423bf23c7a58133970e223b1f47ec6570308 – < a94e62b7c7018fcfe0251e53fa96af30f12d923a
- affected 1296423bf23c7a58133970e223b1f47ec6570308 – < 02647d98340738f918690ed227fdcf154db1b84a
- affected 1296423bf23c7a58133970e223b1f47ec6570308 – < f556bc844cc4423e5ad41ae41a4c24f1cf75b978
- affected 1296423bf23c7a58133970e223b1f47ec6570308 – < 114b42507b6a23d9d24e24e4ef165233332c64d4
- affected 4.17
- unaffected < 4.17
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.103 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/07b52a41765722ec971e0cd9739b140bf4933998 (opens in a new tab)
- https://git.kernel.org/stable/c/a94e62b7c7018fcfe0251e53fa96af30f12d923a (opens in a new tab)
- https://git.kernel.org/stable/c/02647d98340738f918690ed227fdcf154db1b84a (opens in a new tab)
- https://git.kernel.org/stable/c/f556bc844cc4423e5ad41ae41a4c24f1cf75b978 (opens in a new tab)
- https://git.kernel.org/stable/c/114b42507b6a23d9d24e24e4ef165233332c64d4 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-67439 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80704)Record last updated .