CVE-2024-46896

drm/amdgpu: don't access invalid sched

MEDIUM
5.5
CVSS Score
Published: January 11, 2025 at 12:35 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
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: don't access invalid sched Since 2320c9e6a768 ("drm/sched: memset() 'job' in drm_sched_job_init()") accessing job->base.sched can produce unexpected results as the initialisation of (*job)->base.sched done in amdgpu_job_alloc is overwritten by the memset. This commit fixes an issue when a CS would fail validation and would be rejected after job->num_ibs is incremented. In this case, amdgpu_ib_free(ring->adev, ...) will be called, which would crash the machine because the ring value is bogus. To fix this, pass a NULL pointer to amdgpu_ib_free(): we can do this because the device is actually not used in this function. The next commit will remove the ring argument completely. (cherry picked from commit 2ae520cb12831d264ceb97c61f72c59d33c0dbd7)

Affected

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

6.1.120 ≤ v < 6.1.1226.12.5 ≤ v < 6.12.76.6.66 ≤ v < 6.6.68166df51487f46b6e997dfeea7ca0c2a970853f072320c9e6a768d135c7b0039995182bb1a4e4fd222da108b4b5fb7ec04d7e951418ed80e97f7c35ad6.1.1206.12.56.13 rc16.13 rc26.13 rc36.6.6687210234e5a273ebf9c4110a6aa82b8221478daa
Vendor states this is fixed in 65501a4fd84ecdc0af863dbb37759242aab9f2dd (fixed)
Vendor states this is fixed in 67291d601f2b032062b1b2f60ffef1b63e10094c (fixed)
Vendor states this is fixed in a93b1020eb9386d7da11608477121b10079c076a (fixed)
Vendor states this is fixed in da6b2c626ae73c303378ce9eaf6e3eaf16c9925a (fixed)
Affected range stops below 6.1.122, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.12.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.68, so it looks safe — our inference, not a vendor statement

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/65501a4fd84ecdc0af863dbb37759242aab9f2dd
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/67291d601f2b032062b1b2f60ffef1b63e10094c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a93b1020eb9386d7da11608477121b10079c076a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/da6b2c626ae73c303378ce9eaf6e3eaf16c9925a
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html

CVSS

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

Quick Info

StatusMODIFIED
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