dbcve.org
Linux KernelOperating system · Linux

CVE-2024-41039

HIGH · 7.8 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 6.1.100 / 6.6.41 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-120

A fixed-size buffer is filled without checking the length of the incoming data, so it overflows into neighbouring memory. This is the classic overflow attackers use to overwrite return addresses and hijack execution. The fix is strict length checks and safe, bounded string and memory functions.

General guidance for the classic buffer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.16, < 6.1.100>= 6.2, < 6.6.41>= 6.7, < 6.9.10= 6.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.100 / 6.6.41 / 6.9.10 or later
Fixed in 6.1.1006.6.416.9.10
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel >= 6.1.100 (for 6.1.x branch), >= 6.6.41 (for 6.2.x-6.5.x branch), >= 6.9.10 (for 6.7.x-6.9.x branch), or >= 6.11 (for 6.10.x branch)

  1. Identify the currently running kernel version using `uname -r`
  2. Check which affected version range your kernel falls into based on the CVE details
  3. Upgrade to a fixed kernel version: for 6.1.x line upgrade to >= 6.1.100, for 6.2.x-6.5.x upgrade to >= 6.6.41, for 6.7.x-6.9.x upgrade to >= 6.9.10, for 6.10.x upgrade to 6.11 or later
  4. On Debian-based systems, use `apt-get update && apt-get upgrade` or check for kernel updates via your package manager
  5. On Red Hat-based systems, use `yum update kernel` or `dnf update kernel`
  6. Reboot the system to load the fixed kernel
  7. Verify the new kernel version is running using `uname -r` and confirm it is beyond the fixed version for your branch
Caveat Kernel upgrades may require rebooting services; ensure application compatibility with newer kernel if running specialized hardware drivers

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41039 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41039 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data