Skip to main content
VulnerabilityPublished Updated

CVE-2026-53313: Linux kernel · drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths

Source GCVE Database

0
Authoritative record:CVE-2026-53313

Not known to be exploited · CVSS 5.5 Medium · fixed in b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22, a71fdbd6e8289e2725d33a9873833459f3b1824f, 4ae3e16f4b3bf64140f773629b765d605ee079a9 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 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
  • ≥ 2631ac1ac328189031d1aefbbd4929050f72fb23, < b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22
Fixed in
  • b37a978e6d8c33fbfa4abc5dcca4c7cfc6d01f22
LinuxLinuxAffected
  • ≥ 2631ac1ac328189031d1aefbbd4929050f72fb23, < a71fdbd6e8289e2725d33a9873833459f3b1824f
Fixed in
  • a71fdbd6e8289e2725d33a9873833459f3b1824f
LinuxLinuxAffected
  • ≥ 2631ac1ac328189031d1aefbbd4929050f72fb23, < 4ae3e16f4b3bf64140f773629b765d605ee079a9
Fixed in
  • 4ae3e16f4b3bf64140f773629b765d605ee079a9
LinuxLinuxAffected
  • ≥ 2631ac1ac328189031d1aefbbd4929050f72fb23, < 2ab18de5ebb11c76bfc8087c5a09fbcccd0dea8a
Fixed in
  • 2ab18de5ebb11c76bfc8087c5a09fbcccd0dea8a
LinuxLinuxAffected
  • ≥ 2631ac1ac328189031d1aefbbd4929050f72fb23, < 1cad9afbb2d559b738b83c498f9c1abdfd327e7f
Fixed in
  • 1cad9afbb2d559b738b83c498f9c1abdfd327e7f
LinuxLinuxAffected
  • =5.14
Fixed in–

AI-suggested

The described fix involves code changes to properly handle NULL pointer checks in the affected functions. If you cannot patch yet, avoid triggering the affected error paths if possible.

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths In dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace(). Both functions check: if (!dc_dmub_srv || !dc_dmub_srv->dmub) and then call DC_LOG_ERROR() inside that block. DC_LOG_ERROR() uses dc_dmub_srv->ctx internally. So if dc_dmub_srv is NULL, the logging itself can dereference a NULL pointer and cause a crash. Fix this by splitting the checks. First check if dc_dmub_srv is NULL and return immediately. Then check dc_dmub_srv->dmub and log the error only when dc_dmub_srv is valid. Fixes the below: ../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed 'dc_dmub_srv' could be null (see line 961) ../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed 'dc_dmub_srv' could be null (see line 1166)

References

Community reviews

Loading reviews…