In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths In… (CVE-2026-53313)
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)
AI Analysis
Technical Summary
The Linux kernel AMD display driver contained a vulnerability where the functions dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace() performed a combined NULL check on dc_dmub_srv and its member dmub. If dc_dmub_srv was NULL, the subsequent call to DC_LOG_ERROR() would dereference dc_dmub_srv->ctx, causing a NULL pointer dereference and kernel crash. The fix involves splitting the NULL checks: first verifying dc_dmub_srv is not NULL before returning early, then checking dc_dmub_srv->dmub and logging errors only if dc_dmub_srv is valid.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel due to a NULL pointer dereference in the AMD display driver's error handling paths. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix involves code changes to properly handle NULL pointer checks in the affected functions. Until an official patch is available, avoid triggering the affected error paths if possible.
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths In… (CVE-2026-53313)
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)
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel AMD display driver contained a vulnerability where the functions dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace() performed a combined NULL check on dc_dmub_srv and its member dmub. If dc_dmub_srv was NULL, the subsequent call to DC_LOG_ERROR() would dereference dc_dmub_srv->ctx, causing a NULL pointer dereference and kernel crash. The fix involves splitting the NULL checks: first verifying dc_dmub_srv is not NULL before returning early, then checking dc_dmub_srv->dmub and logging errors only if dc_dmub_srv is valid.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel due to a NULL pointer dereference in the AMD display driver's error handling paths. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix involves code changes to properly handle NULL pointer checks in the affected functions. Until an official patch is available, avoid triggering the affected error paths if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2885-rcqv-3jp6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53313"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c33fe27e9c797195f459d
Added to database: 07/06/2026, 23:02:22 UTC
Last enriched: 07/06/2026, 23:09:58 UTC
Last updated: 07/31/2026, 19:24:48 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.