CVE-2024-53060

drm/amdgpu: prevent NULL pointer dereference if ATIF is not supported

MEDIUM

5.5

CVSS Score

Published: November 19, 2024 at 05:22 PM UTC

Updated: June 17, 2026 at 08:08 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: prevent NULL pointer dereference if ATIF is not supported acpi_evaluate_object() may return AE_NOT_FOUND (failure), which would result in dereferencing buffer.pointer (obj) while being NULL. Although this case may be unrealistic for the current code, it is still better to protect against possible bugs. Bail out also when status is AE_NOT_FOUND. This fixes 1 FORWARD_NULL issue reported by Coverity Report: CID 1600951: Null pointer dereferences (FORWARD_NULL) (cherry picked from commit 91c9e221fe2553edf2db71627d8453f083de87a1)

Affected

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

Linux Kernel · Linux

95%

v < 4.19.3244.19.323 ≤ v < 4.19.3244.20 ≤ v < 5.4.2865.10.229 ≤ v < 5.10.2305.11 ≤ v < 5.15.1725.15.170 ≤ v < 5.15.1725.16 ≤ v < 6.1.1175.4.285 ≤ v < 5.4.2865.5 ≤ v < 5.10.2306.1.115 ≤ v < 6.1.1176.11.6 ≤ v < 6.11.86.2 ≤ v < 6.6.616.6.59 ≤ v < 6.6.616.7 ≤ v < 6.11.81d7175f9c57b1abf9ecfbdfd53ea760761f52ffe234682910971732cd4da96fd95946e296e486b384.19.32343b4fa6e0e238c6e2662f4fb61d9f51c2785fb1d5.10.229 5.15.170 5.4.28558556dcbd5606a5daccaee73b2130bc16b48e0256.1.115 6.11.6 6.12 rc1 6.12 rc2 6.12 rc3 6.12 rc4 6.12 rc5 6.12 rc6 6.6.596032287747f874b52dc8b9d7490e2799736e035f975ede2a7bec52b5da1428829b3439667c8a234bbf58f03931fdcf7b3c45cb76ac13244477a60f44cd67af3c1762de4c2483ae4dbdd98f9ea8fa56e3

Vendor states this is fixed in 1a9f55ed5b512f510ccd21ad527d532e60550e80 (fixed)

Vendor states this is fixed in 27fc29b5376998c126c85cf9b15d9dfc2afc9cbe (fixed)

Vendor states this is fixed in 2ac7f253deada4d449559b65a1c1cd0a6f6f19b7 (fixed)

Vendor states this is fixed in 8d7a28eca7553d35d4ce192fa1f390f2357df41b (fixed)

Vendor states this is fixed in a613a392417532ca5aaf3deac6e3277aa7aaef2b (fixed)

Vendor states this is fixed in a6dd15981c03f2cdc9a351a278f09b5479d53d2e (fixed)

Vendor states this is fixed in b9d9881237afeb52eddd70077b7174bf17e2fa30 (fixed)

Vendor states this is fixed in ce8a00a00e36f61f5a1e47734332420b68784c43 (fixed)

Affected range stops below 4.19.324, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.10.230, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.15.172, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.286, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.117, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.11.8, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.6.61, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

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

Patch and advisory references