CVE-2024-46896
published 2025-01-11CVE-2024-46896: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: don't access invalid sched Since 2320c9e6a768 ("drm/sched: memset() 'job' in…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.6th percentile
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
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.123-1 (bookworm) | linux 6.1.123-1 (bookworm) |
| debian | linux-6.1 | < linux 6.1.123-1 (bookworm) | linux 6.1.123-1 (bookworm) |
| linux | linux | >= 166df51487f46b6e997dfeea7ca0c2a970853f07 < 65501a4fd84ecdc0af863dbb37759242aab9f2dd | 65501a4fd84ecdc0af863dbb37759242aab9f2dd |
| linux | linux | >= 2320c9e6a768d135c7b0039995182bb1a4e4fd22 < a93b1020eb9386d7da11608477121b10079c076a | a93b1020eb9386d7da11608477121b10079c076a |
| linux | linux | >= 2da108b4b5fb7ec04d7e951418ed80e97f7c35ad < 67291d601f2b032062b1b2f60ffef1b63e10094c | 67291d601f2b032062b1b2f60ffef1b63e10094c |
| linux | linux | >= 6.1.120 < 6.1.122 | 6.1.122 |
| linux | linux | >= 6.12.5 < 6.12.7 | 6.12.7 |
| linux | linux | >= 6.6.66 < 6.6.68 | 6.6.68 |
| linux | linux | >= 87210234e5a273ebf9c4110a6aa82b8221478daa < da6b2c626ae73c303378ce9eaf6e3eaf16c9925a | da6b2c626ae73c303378ce9eaf6e3eaf16c9925a |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.123-1 | 6.1.123-1 |
| linux | linux_kernel | >= 0 < 6.12.8-1 | 6.12.8-1 |
| linux | linux_kernel | >= 0 < 6.12.8-1 | 6.12.8-1 |
| linux | linux_kernel | >= 6.1.120 < 6.1.122 | 6.1.122 |
| linux | linux_kernel | >= 6.12.5 < 6.12.7 | 6.12.7 |
| linux | linux_kernel | >= 6.6.66 < 6.6.68 | 6.6.68 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: drm/amdgpu: don't access invalid sched
vendor_redhat·2025-01-11·CVSS 5.5
CVE-2024-46896 [MEDIUM] CWE-119 kernel: drm/amdgpu: don't access invalid sched
kernel: drm/amdgpu: don't access invalid sched
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 co
Debian
CVE-2024-46896: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu:...
vendor_debian·2024·CVSS 5.5
CVE-2024-46896 [MEDIUM] CVE-2024-46896: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu:...
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 2ae520cb128
GHSA
GHSA-vjgg-3f8r-g7rm: In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: don't access invalid sched
Since 2320c9e6a768 ("drm/sched: memset()
ghsa_unreviewed·2025-01-11
CVE-2024-46896 [MEDIUM] CWE-476 GHSA-vjgg-3f8r-g7rm: In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: don't access invalid sched
Since 2320c9e6a768 ("drm/sched: memset()
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 2ae52
OSV
CVE-2024-46896: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: don't access invalid sched Since 2320c9e6a768 ("drm/sched: memset() 'j
osv·2025-01-11·CVSS 5.5
CVE-2024-46896 [MEDIUM] CVE-2024-46896: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: don't access invalid sched Since 2320c9e6a768 ("drm/sched: memset() 'j
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 2ae520cb128
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/65501a4fd84ecdc0af863dbb37759242aab9f2ddhttps://git.kernel.org/stable/c/67291d601f2b032062b1b2f60ffef1b63e10094chttps://git.kernel.org/stable/c/a93b1020eb9386d7da11608477121b10079c076ahttps://git.kernel.org/stable/c/da6b2c626ae73c303378ce9eaf6e3eaf16c9925ahttps://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
2025-01-11
Published