CVE-2024-46896
Last modified
CVE-2024-46896 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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). EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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)
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.1.120, < 6.1.122 | — |
| Linux | Linux Kernel | >= 6.6.66, < 6.6.68 | — |
| Linux | Linux Kernel | >= 6.12.5, < 6.12.7 | — |
| Linux | Linux Kernel | 6.13 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-46896?
How severe is CVE-2024-46896?
How do I fix CVE-2024-46896?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-4689Cross-Site Request Forgery (CSRF) vulnerability in ShortPixe…4.3
- CVE-2024-46890A vulnerability has been identified in SINEC INS (All versio…9.4
- CVE-2024-46891A vulnerability has been identified in SINEC INS (All versio…7.5
- CVE-2024-46892A vulnerability has been identified in SINEC INS (All versio…8.1
- CVE-2024-46894A vulnerability has been identified in SINEC INS (All versio…5.4
- CVE-2024-46895Uncontrolled search path for some Intel(R) Arc™ & Iris(R…6.7
- CVE-2024-46897Incorrect permission assignment for critical resource issue …3.8
- CVE-2024-46898SHIRASAGI prior to v1.19.1 processes URLs in HTTP requests i…7.5
- CVE-2024-46899Hitachi Ops Center Common Services within Hitachi Ops Center…7.1
- CVE-2024-4690Improper Restriction of XML External Entity Reference vulner…8
- CVE-2024-46901Insufficient validation of filenames against control charact…4.3
- CVE-2024-46902A vulnerability in Trend Micro Deep Discovery Inspector (DDI…9.1
Are you affected by CVE-2024-46896?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
