Bug 2337353 (CVE-2024-46896) - CVE-2024-46896 kernel: drm/amdgpu: don't access invalid sched
Summary: CVE-2024-46896 kernel: drm/amdgpu: don't access invalid sched
Keywords:
Status: NEW
Alias: CVE-2024-46896
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-13 12:01 UTC by OSIDB Bzimport
Modified: 2025-01-13 12:50 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-01-13 12:01:36 UTC
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)

Comment 1 Avinash Hanwate 2025-01-13 12:46:54 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025011141-CVE-2024-46896-8e7c@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.