Bug 2271796 (CVE-2024-26649) - CVE-2024-26649 kernel: null pointer when load rlc firmware
Summary: CVE-2024-26649 kernel: null pointer when load rlc firmware
Keywords:
Status: NEW
Alias: CVE-2024-26649
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2271802
Blocks: 2271799 2271782
TreeView+ depends on / blocked
 
Reported: 2024-03-27 11:41 UTC by Rohit Keshri
Modified: 2024-08-21 09:44 UTC (History)
50 users (show)

Fixed In Version: kernel 6.6.15, kernel 6.7.3, kernel 6.8
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in the drm/amdgpu driver of Linux Kernel, causing null pointer dereference when attempting to load RLC (Run-Length Coding) firmware. This issue arises if the firmware has an incorrect header size, causing premature release of the firmware pointer in amdgpu_ucode_request(), subsequently attempts to use the nullified pointer result in errors.
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Rohit Keshri 2024-03-27 11:41:46 UTC 
In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: Fix the null pointer when load rlc firmware

If the RLC firmware is invalid because of wrong header size,
the pointer to the rlc firmware is released in function
amdgpu_ucode_request. There will be a null pointer error
in subsequent use. So skip validation to fix it.

https://git.kernel.org/stable/c/8b5bacce2d13dbe648f0bfd3f738ecce8db4978c
https://git.kernel.org/stable/c/bc03c02cc1991a066b23e69bbcc0f66e8f1f7453
https://git.kernel.org/stable/c/d3887448486caeef9687fb5dfebd4ff91e0f25aa
Comment 1 Rohit Keshri 2024-03-27 11:55:02 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2271802]
Comment 4 Justin M. Forbes 2024-03-27 20:21:48 UTC 
This was fixed for Fedora with the 6.7.3 stable kernel updates.
Comment 5 Alex 2024-06-09 13:02:10 UTC 
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2024-26649 is: 	SKIP	The Fixes patch not applied yet, so unlikely that actual: 3da9b71563cbb7281875adab1d7c4132679da987	YES			NO	YES	unknown (where first YES/NO value means if related sources built).
Note You need to log in before you can comment on or make changes to this bug.