CVE-2024-50104

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2024-11-05. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-44579 (ENISA EUVD) · GHSA-v95w-jfg2-cj6w (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ASoC: qcom: sdm845: add missing soundwire runtime stream alloc

During the migration of Soundwire runtime stream allocation from the Qualcomm Soundwire controller to SoC's soundcard drivers the sdm845 soundcard was forgotten.

At this point any playback attempt or audio daemon startup, for instance on sdm845-db845c (Qualcomm RB3 board), will result in stream pointer NULL dereference:

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=0000000101ecf000 [0000000000000020] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: ... CPU: 5 UID: 0 PID: 1198 Comm: aplay Not tainted 6.12.0-rc2-qcomlt-arm64-00059-g9d78f315a362-dirty #18 Hardware name: Thundercomm Dragonboard 845c (DT) pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : sdw_stream_add_slave+0x44/0x380 [soundwire_bus] lr : sdw_stream_add_slave+0x44/0x380 [soundwire_bus] sp : ffff80008a2035c0 x29: ffff80008a2035c0 x28: ffff80008a203978 x27: 0000000000000000 x26: 00000000000000c0 x25: 0000000000000000 x24: ffff1676025f4800 x23: ffff167600ff1cb8 x22: ffff167600ff1c98 x21: 0000000000000003 x20: ffff167607316000 x19: ffff167604e64e80 x18: 0000000000000000 x17: 0000000000000000 x16: ffffcec265074160 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 x8 : 0000000000000000 x7 : 0000000000000000 x6 : ffff167600ff1cec x5 : ffffcec22cfa2010 x4 : 0000000000000000 x3 : 0000000000000003 x2 : ffff167613f836c0 x1 : 0000000000000000 x0 : ffff16761feb60b8 Call trace: sdw_stream_add_slave+0x44/0x380 [soundwire_bus] wsa881x_hw_params+0x68/0x80 [snd_soc_wsa881x] snd_soc_dai_hw_params+0x3c/0xa4 __soc_pcm_hw_params+0x230/0x660 dpcm_be_dai_hw_params+0x1d0/0x3f8 dpcm_fe_dai_hw_params+0x98/0x268 snd_pcm_hw_params+0x124/0x460 snd_pcm_common_ioctl+0x998/0x16e8 snd_pcm_ioctl+0x34/0x58 __arm64_sys_ioctl+0xac/0xf8 invoke_syscall+0x48/0x104 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x34/0xe0 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x190/0x194 Code: aa0403fb f9418400 9100e000 9400102f (f8420f22) ---[ end trace 0000000000000000 ]---

0000000000006108 : 6108: d503233f paciasp 610c: a9b97bfd stp x29, x30, [sp, #-112]! 6110: 910003fd mov x29, sp 6114: a90153f3 stp x19, x20, [sp, #16] 6118: a9025bf5 stp x21, x22, [sp, #32] 611c: aa0103f6 mov x22, x1 6120: 2a0303f5 mov w21, w3 6124: a90363f7 stp x23, x24, [sp, #48] 6128: aa0003f8 mov x24, x0 612c: aa0203f7 mov x23, x2 6130: a9046bf9 stp x25, x26, [sp, #64] 6134: aa0403f9 mov x25, x4 <-- x4 copied to x25 6138: a90573fb stp x27, x28, [sp, #80] 613c: aa0403fb mov x27, x4 6140: f9418400 ldr x0, [x0, #776] 6144: 9100e000 add x0, x0, #0x38 6148: 94000000 bl 0 614c: f8420f22 ldr x2, [x25, #32]! <-- offset 0x44 ^^^ This is 0x6108 + offset 0x44 from the beginning of sdw_stream_add_slave() where data abort happens. wsa881x_hw_params() is called with stream = NULL and passes it further in register x4 (5th argu ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 5, 2024

Last Modified

October 1, 2025

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.6-1: fixed in 6.11.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.6-1: fixed in 6.11.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 7× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 206 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 112 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-25 16:59 UTCEG score recompute
  9. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-24 04:13 UTCEG score recompute
  12. 2026-10-24 04:13 UTCVendor advisory
  13. 2026-10-24 04:12 UTCGHSA enrichmentGHSA-v95w-jfg2-cj6w · GitHub CVSS 5.5
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-18 06:55 UTCEG score recompute
  21. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-12 17:41 UTCEG score recompute
Show 69 more
  1. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-11 21:07 UTCEG score recompute
  3. 2026-10-11 15:59 UTCEG score recompute
  4. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-10 09:55 UTCOSV refresh
  7. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-02 16:15 UTCEG score recompute
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-20 19:14 UTCOSV refresh
  26. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  30. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  32. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  37. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  40. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  42. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  43. 2026-09-01 19:05 UTCOSV refresh
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  45. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  47. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  49. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  50. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  51. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  52. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  59. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  61. 2026-08-15 20:37 UTCOSV refresh
  62. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  63. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  64. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  65. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  66. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  67. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  68. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  69. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile

Frequently asked(5)

What is CVE-2024-50104?
CVE-2024-50104 is a medium-severity vulnerability; its CVE record was published on November 5, 2024. In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: sdm845: add missing soundwire runtime stream alloc During the migration of Soundwire runtime stream allocation from the Qualcomm Soundwire controller to SoC's soundcard drivers the sdm845 soundcard was forgotten. At…
When was the CVE record for CVE-2024-50104 published?
The CVE record for CVE-2024-50104 was published on November 5, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 1, 2025; the record at its source may have been updated since.
Is CVE-2024-50104 actively exploited?
CVE-2024-50104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50104?
CVE-2024-50104 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-50104?
A fix for CVE-2024-50104 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-50104

Explore →

Is Your Infrastructure Affected by CVE-2024-50104?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.