CVE-2024-50175

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-08. 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-44677 (ENISA EUVD) · GHSA-8pr8-xc5p-c8gp (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:

media: qcom: camss: Remove use_count guard in stop_streaming

The use_count check was introduced so that multiple concurrent Raw Data Interfaces RDIs could be driven by different virtual channels VCs on the CSIPHY input driving the video pipeline.

This is an invalid use of use_count though as use_count pertains to the number of times a video entity has been opened by user-space not the number of active streams.

If use_count and stream-on count don't agree then stop_streaming() will break as is currently the case and has become apparent when using CAMSS with libcamera's released softisp 0.3.

The use of use_count like this is a bit hacky and right now breaks regular usage of CAMSS for a single stream case. Stopping qcam results in the splat below, and then it cannot be started again and any attempts to do so fails with -EBUSY.

[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] ... [ 1265.510630] Call trace: [ 1265.510636] __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] [ 1265.510648] vb2_core_streamoff+0x24/0xcc [videobuf2_common] [ 1265.510660] vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2] [ 1265.510673] v4l_streamoff+0x24/0x30 [videodev] [ 1265.510707] __video_do_ioctl+0x190/0x3f4 [videodev] [ 1265.510732] video_usercopy+0x304/0x8c4 [videodev] [ 1265.510757] video_ioctl2+0x18/0x34 [videodev] [ 1265.510782] v4l2_ioctl+0x40/0x60 [videodev] ... [ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state [ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state [ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st

One CAMSS specific way to handle multiple VCs on the same RDI might be:

  • Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.
  • The video buffers are already associated with msm_vfeN_rdiX so
release video buffers when told to do so by stop_streaming.
  • Only release the power-domains for the CSIPHY, CSID and VFE when
their internal refcounts drop.

Either way refusing to release video buffers based on use_count is erroneous and should be reverted. The silicon enabling code for selecting VCs is perfectly fine. Its a "known missing feature" that concurrent VCs won't work with CAMSS right now.

Initial testing with this code didn't show an error but, SoftISP and "real" usage with Google Hangouts breaks the upstream code pretty quickly, we need to do a partial revert and take another pass at VCs.

This commit partially reverts commit 89013969e232 ("media: camss: sm8250: Pipeline starting and stopping for multiple virtual channels")

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
13th
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 8, 2024

Last Modified

August 5, 2026

References (4)

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual (6.8.0-54.56) @ noble2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1006.8) @ noble2026-10-24ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-10-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1022.25.2) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1019.23) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1020.21) @ noble2026-10-24ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1023.25) @ noble2026-10-24ubuntu
linuxKernel @ 6.6.55 (fixes >=6.4.0)—osv

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.4-1: fixed in 6.11.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.4-1: fixed in 6.11.4-1
—

All Vendor Advisories

(11)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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 215 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 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-50175?
CVE-2024-50175 is a medium-severity vulnerability; its CVE record was published on November 8, 2024. In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: Remove use_count guard in stop_streaming The use_count check was introduced so that multiple concurrent Raw Data Interfaces RDIs could be driven by different virtual channels VCs on the CSIPHY input driving the…
When was the CVE record for CVE-2024-50175 published?
The CVE record for CVE-2024-50175 was published on November 8, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-50175 actively exploited?
CVE-2024-50175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50175?
CVE-2024-50175 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-50175?
A fix for CVE-2024-50175 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-50175

Explore →

Is Your Infrastructure Affected by CVE-2024-50175?

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

Book a Demo →Browse All CVEs