CVE-2024-49901

drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs

MEDIUM
5.5
CVSS Score
Published: October 21, 2024 at 06:01 PM UTC
Updated: June 17, 2026 at 08:00 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
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs There are some cases, such as the one uncovered by Commit 46d4efcccc68 ("drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails") where msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL); is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet. Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT). Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so. Patchwork: https://patchwork.freedesktop.org/patch/602742/

Affected

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

v < 6.6.553.12 ≤ v < 6.10.143.12 ≤ v < 6.11.33.12 ≤ v < 6.123.12 ≤ v < 6.6.556.11 ≤ v < 6.11.36.7 ≤ v < 6.10.140cf6c71d70d8aa39b8fd0e39c9009602a0e0d3003.12
Vendor states this is fixed in 16007768551d5bfe53426645401435ca8d2ef54f (fixed)
Vendor states this is fixed in 9288a9676c529ad9c856096db68fad812499bc4a (fixed)
Vendor states this is fixed in 9773737375b20070ea935203fd66cb9fa17c5acb (fixed)
Vendor states this is fixed in e8ac2060597a5768e4699bb61d604b4c09927b85 (fixed)
Vendor states this is fixed in 3.12 (unaffected)
Vendor states this is fixed in 6.10.14 (unaffected)
Vendor states this is fixed in 6.11.3 (unaffected)
Vendor states this is fixed in 6.12 (unaffected)
Vendor states this is fixed in 6.6.55 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/16007768551d5bfe53426645401435ca8d2ef54f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9288a9676c529ad9c856096db68fad812499bc4a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9773737375b20070ea935203fd66cb9fa17c5acb
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e8ac2060597a5768e4699bb61d604b4c09927b85

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
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

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