CVE-2024-44955: drm/amd/display: Don't refer to dc_sink in is_dsc_need_re_compute
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Don't refer to dcsink in isdscneedrecompute
[Why] When unplug one of monitors connected after mst hub, encounter null pointer dereference.
It's due to dcsink get released immediately in earlyunregister() or detectctx(). When commit new state which directly referring to info stored in dcsink will cause null pointer dereference.
[how] Remove redundant checking condition. Relevant condition should already be covered by checking if dscaux is null or not. Also reset dscaux to NULL when the connector is disconnected.
Other sources
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
— NVD
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-44955?
CVE-2024-44955 has been classified with a severity that necessitates prompt attention due to its potential impact on system stability.
How do I fix CVE-2024-44955?
To fix CVE-2024-44955, upgrade the Linux kernel to version 6.10.5 or later, where this vulnerability has been resolved.
What does CVE-2024-44955 affect?
CVE-2024-44955 affects the Linux kernel prior to version 6.10.5, specifically regarding display handling when monitors are unplugged.
What exploit does CVE-2024-44955 enable?
CVE-2024-44955 could potentially enable a null pointer dereference when a monitor is unplugged, leading to a system crash.
Was CVE-2024-44955 actively exploited in the wild?
As of now, there are no confirmed reports indicating that CVE-2024-44955 has been actively exploited in the wild.