CVE-2024-41039: firmware: cs_dsp: Fix overflow checking of wmfw header
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3019b86bce16fbb5bc1964f3544d0ce7d0137278, 49a79f344d0a17c6a5eef53716cc76fcdbfca9ba, 9c9877a96e033bf6c6470b3b4f06106d91ace11e.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3019b86bce16fbb5bc1964f3544d0ce7d0137278, 49a79f344d0a17c6a5eef53716cc76fcdbfca9ba, 9c9877a96e033bf6c6470b3b4f06106d91ace11e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 29, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-120
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.16affected
- f6bc909e7673c30abcbdb329e7d0aa2e83c103d7 and later · before fd035f0810b33c2a8792effdb82bf35920221565affected · git
- f6bc909e7673c30abcbdb329e7d0aa2e83c103d7 and later · before 9c9877a96e033bf6c6470b3b4f06106d91ace11eaffected · git
- f6bc909e7673c30abcbdb329e7d0aa2e83c103d7 and later · before 49a79f344d0a17c6a5eef53716cc76fcdbfca9baaffected · git
- f6bc909e7673c30abcbdb329e7d0aa2e83c103d7 and later · before 3019b86bce16fbb5bc1964f3544d0ce7d0137278affected · git
- before 5.16not affected · semver
- 6.1.100 and later · up to and including 6.1.*not affected · semver
- 6.6.41 and later · up to and including 6.6.*not affected · semver
- 6.9.10 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.16 and later · before 6.1.100
- linux linux kernel6.2 and later · before 6.6.41
- linux linux kernel6.7 and later · before 6.9.10
- linux linux kernel6.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.9.10-1 | 6.9.10-1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.92.1.el9_2 | 0:7.0.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | perf | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-41037Jul 29, 2024 · ASoC: SOF: Intel: hda: fix null deref on system suspend entry22Monitor
- ← EarlierCVE-2024-41038Jul 29, 2024 · firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers22Monitor
- Later →CVE-2024-41040Jul 29, 2024 · net/sched: Fix UAF when resolving a clash28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3019b86bce16fbb5bc1964f3544d0ce7d0137278 | Vendor (CNA) |
| Linux Linux | 49a79f344d0a17c6a5eef53716cc76fcdbfca9ba | Vendor (CNA) |
| Linux Linux | 9c9877a96e033bf6c6470b3b4f06106d91ace11e | Vendor (CNA) |
| Linux Linux | fd035f0810b33c2a8792effdb82bf35920221565 | Vendor (CNA) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-44466304 days apartAn issue was discovered in net/ceph/messenger_v2.c in the Linux kernel before 6.4.5.48Plan
- CVE-2023-5273569 days apartbpf, sockmap: Don't let sock_map_{close,destroy,unhash} call itself36Monitor
- CVE-2024-2692792 days apartASoC: SOF: Add some bounds checking to firmware data33Monitor
- CVE-2024-4090217 days apartjfs: xattr: fix buffer overflow for invalid xattr31Monitor
- CVE-2024-3948024 days apartkdb: Fix buffer overflow during tab-complete31Monitor
- CVE-2024-3929135 days apartdrm/amdgpu: Fix buffer size in gfx_v9_4_3_init_ cp_compute_microcode() and rlc_microcode()31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1094 · Jul 30, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.