CVE-2024-46870

drm/amd/display: Disable DMCUB timeout for DCN35

MEDIUM
4.7
CVSS Score
Published: October 9, 2024 at 02:02 PM UTC
Updated: June 17, 2026 at 07:56 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.7
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Disable DMCUB timeout for DCN35 [Why] DMCUB can intermittently take longer than expected to process commands. Old ASIC policy was to continue while logging a diagnostic error - which works fine for ASIC without IPS, but with IPS this could lead to a race condition where we attempt to access DCN state while it's inaccessible, leading to a system hang when the NIU port is not disabled or register accesses that timeout and the display configuration in an undefined state. [How] We need to investigate why these accesses take longer than expected, but for now we should disable the timeout on DCN35 to avoid this race condition. Since the waits happen only at lower interrupt levels the risk of taking too long at higher IRQ and causing a system watchdog timeout are minimal.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.15 ≤ v < 4.19.3234.15 ≤ v < 6.10.94.15 ≤ v < 6.114.20 ≤ v < 5.4.2855.11 ≤ v < 5.15.1685.16 ≤ v < 6.1.1125.5 ≤ v < 5.10.2276.2 ≤ v < 6.6.536.7 ≤ v < 6.10.124.154562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c
Vendor states this is fixed in 31c254c9cd4b122a10db297124f867107a696d83 (fixed)
Vendor states this is fixed in 7c70e60fbf4bff1123f0e8d5cb1ae71df6164d7f (fixed)
Vendor states this is fixed in 4.15 (unaffected)
Vendor states this is fixed in 6.10.9 (unaffected)
Vendor states this is fixed in 6.11 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/31c254c9cd4b122a10db297124f867107a696d83
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7c70e60fbf4bff1123f0e8d5cb1ae71df6164d7f

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card