CVE-2024-41039

firmware: cs_dsp: Fix overflow checking of wmfw header

HIGH
7.8
CVSS Score
Published: July 29, 2024 at 02:31 PM UTC
Updated: June 17, 2026 at 07:47 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.16 ≤ v < 6.1.1005.16 ≤ v < 6.105.16 ≤ v < 6.6.415.16 ≤ v < 6.9.106.2 ≤ v < 6.6.416.7 ≤ v < 6.9.106.10 rc16.10 rc26.10 rc36.10 rc46.10 rc56.10 rc66.10 rc7f6bc909e7673c30abcbdb329e7d0aa2e83c103d7
Vendor states this is fixed in 3019b86bce16fbb5bc1964f3544d0ce7d0137278 (fixed)
Vendor states this is fixed in 49a79f344d0a17c6a5eef53716cc76fcdbfca9ba (fixed)
Vendor states this is fixed in 9c9877a96e033bf6c6470b3b4f06106d91ace11e (fixed)
Vendor states this is fixed in fd035f0810b33c2a8792effdb82bf35920221565 (fixed)
Vendor states this is fixed in 5.16 (unaffected)
Vendor states this is fixed in 6.1.100 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.6.41 (unaffected)
Vendor states this is fixed in 6.9.10 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3019b86bce16fbb5bc1964f3544d0ce7d0137278
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/49a79f344d0a17c6a5eef53716cc76fcdbfca9ba
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9c9877a96e033bf6c6470b3b4f06106d91ace11e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fd035f0810b33c2a8792effdb82bf35920221565
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-120

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card