CVE-2024-43904: drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Add null checks for 'stream' and 'plane' before dereferencing
This commit adds null checks for the 'stream' and 'plane' variables in
the dcn30_apply_idle_power_optimizations function. These variables were
previously assumed to be null at line 922, but they were used later in
the code without checking if they were null. This could potentially lead
to a null pointer dereference, which would cause a crash.
The null checks ensure that 'stream' and 'plane' are not null before
they are used, preventing potential crashes.
Fixes the below static smatch checker:
drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:938 dcn30_apply_idle_power_optimizations() error: we previously assumed 'stream' could be null (see line 922)
drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:940 dcn30_apply_idle_power_optimizations() error: we previously assumed 'plane' could be null (see line 922)
Security readout for executives and security teams
Plain-English summary
CVE-2024-43904 is a Linux kernel AMD display driver bug that can crash affected systems when display idle power optimization code dereferences missing stream or plane data. The public record describes a null-pointer crash, not data theft or remote takeover. Business urgency depends on affected Linux devices with AMD graphics.
Executive priority
Do not treat this as an emergency based on current evidence, but include it in normal kernel patch cycles. Escalate priority for systems where a display crash could disrupt revenue, safety monitoring, customer-facing kiosks, or operational workstations.
Technical view
In drivers/gpu/drm/amd/display/dc/hwss/dcn30/dcn30_hwseq.c, dcn30_apply_idle_power_optimizations() treated stream and plane as nullable, then later used them without null checks. Stable fixes add guard checks before dereference. The described impact is null pointer dereference and crash; broader exploitability is not established.
Likely exposure
Likely limited to Linux systems running affected kernel versions with the AMDGPU display stack, especially AMD graphics endpoints, workstations, kiosks, or GUI hosts. Headless Linux servers without AMD display hardware or driver loading are less likely exposed, but confirm with asset and kernel inventory.
Exploitation context
The bundle does not show CISA KEV listing, public active exploitation, or exploit code. The issue was identified by the smatch static checker and fixed in Linux stable commits. Treat exploitation likelihood as unproven, while recognizing kernel crashes can still affect availability.
Researcher notes
The record names one bug class: unchecked stream and plane pointers in dcn30_apply_idle_power_optimizations(). The sources do not define attacker prerequisites, privilege level, trigger path, CVSS, or confidentiality/integrity impact. Validation should focus on affected kernel lineage and availability symptoms.
Mitigation direction
Update affected Linux kernels to vendor packages containing the referenced stable fixes.
Prioritize AMD graphics systems supporting business-critical desktops, displays, kiosks, or graphical workloads.
Use distribution advisories, including Debian LTS where applicable, to confirm fixed package versions.
If patching is delayed, check vendor guidance for supported temporary risk-reduction options.
Avoid unsupported kernel cherry-picks unless your kernel maintenance process already validates them.
Validation and detection
Inventory Linux kernel versions across AMD GPU or display-enabled assets.
Confirm whether the AMDGPU display driver is present and loaded on those systems.
Compare running kernels against vendor fixed versions or the referenced stable commits.
Review kernel logs for null-pointer crashes in drm/amd/display paths.
Verify patched systems remain stable under normal display idle and resume behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-43904 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.