Skip to main content
VulnerabilityPublished Updated

CVE-2026-80704: Linux kernel · drm/amd/display: use proper context for logging

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f556bc844cc4423e5ad41ae41a4c24f1cf75b978 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f556bc844cc4423e5ad41ae41a4c24f1cf75b978, a94e62b7c7018fcfe0251e53fa96af30f12d923a, 02647d98340738f918690ed227fdcf154db1b84a +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1296423bf23c7a58133970e223b1f47ec6570308, < f556bc844cc4423e5ad41ae41a4c24f1cf75b978
Fixed in
  • f556bc844cc4423e5ad41ae41a4c24f1cf75b978
LinuxLinuxAffected
  • ≥ 1296423bf23c7a58133970e223b1f47ec6570308, < a94e62b7c7018fcfe0251e53fa96af30f12d923a
Fixed in
  • a94e62b7c7018fcfe0251e53fa96af30f12d923a
LinuxLinuxAffected
  • ≥ 1296423bf23c7a58133970e223b1f47ec6570308, < 02647d98340738f918690ed227fdcf154db1b84a
Fixed in
  • 02647d98340738f918690ed227fdcf154db1b84a
LinuxLinuxAffected
  • ≥ 1296423bf23c7a58133970e223b1f47ec6570308, < 114b42507b6a23d9d24e24e4ef165233332c64d4
Fixed in
  • 114b42507b6a23d9d24e24e4ef165233332c64d4
LinuxLinuxAffected
  • ≥ 1296423bf23c7a58133970e223b1f47ec6570308, < 07b52a41765722ec971e0cd9739b140bf4933998
Fixed in
  • 07b52a41765722ec971e0cd9739b140bf4933998
LinuxLinuxAffected
  • =4.17
Fixed in–

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)

References

Community reviews

Loading reviews…