Heap-based Buffer Overflow Affecting kernel-headers package, versions <0:4.18.0-553.22.1.el8_10
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS8-KERNELHEADERS-7600784
- published 5 Aug 2024
- disclosed 29 Jul 2024
Introduced: 29 Jul 2024
CVE-2024-41039 Open this link in a new tabHow to fix?
Upgrade Centos:8
kernel-headers
to version 0:4.18.0-553.22.1.el8_10 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-headers
package and not the kernel-headers
package as distributed by Centos
.
See How to fix?
for Centos:8
relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
firmware: cs_dsp: Fix overflow checking of wmfw header
Fix the checking that firmware file buffer is large enough for the wmfw header, to prevent overrunning the buffer.
The original code tested that the firmware data buffer contained enough bytes for the sums of the size of the structs
wmfw_header + wmfw_adsp1_sizes + wmfw_footer
But wmfw_adsp1_sizes is only used on ADSP1 firmware. For ADSP2 and Halo Core the equivalent struct is wmfw_adsp2_sizes, which is 4 bytes longer. So the length check didn't guarantee that there are enough bytes in the firmware buffer for a header with wmfw_adsp2_sizes.
This patch splits the length check into three separate parts. Each of the wmfw_header, wmfw_adsp?_sizes and wmfw_footer are checked separately before they are used.
References
- https://access.redhat.com/security/cve/CVE-2024-41039
- https://git.kernel.org/stable/c/3019b86bce16fbb5bc1964f3544d0ce7d0137278
- https://git.kernel.org/stable/c/49a79f344d0a17c6a5eef53716cc76fcdbfca9ba
- https://git.kernel.org/stable/c/9c9877a96e033bf6c6470b3b4f06106d91ace11e
- https://git.kernel.org/stable/c/fd035f0810b33c2a8792effdb82bf35920221565