Security readout for executives and security teams
Plain-English summary
A Linux camera-driver bug can leave camera buffers active when streaming stops on systems using Qualcomm CAMSS. Normal camera applications may trigger kernel warnings and leave the camera unavailable with EBUSY until recovery. The supplied CVSS score is 7.8, but practical exposure depends on affected kernel code and Qualcomm camera hardware being present.
Executive priority
Prioritize affected Qualcomm camera devices, especially production endpoints where camera availability or kernel stability matters. Patch through normal kernel maintenance promptly. Broader emergency action is not supported because exposure is hardware-specific and the supplied evidence does not show active exploitation.
Technical view
CAMSS stop_streaming() incorrectly used a video entity use_count as an active-stream count. When open and streaming counts diverged, buffer release was skipped, violating videobuf2 requirements and leaving buffers active. The resolution removes that guard, partially reverting the earlier multiple-virtual-channel change. Reported triggers include libcamera SoftISP, qcam, and Google Hangouts use.
Likely exposure
Exposure is concentrated in Linux devices running the affected CAMSS code with supported Qualcomm camera hardware. The bundle lists affected versions including 6.4, 6.6.55, 6.10.14, 6.11.3, and 6.12, but its version data is ambiguous; verify each vendor kernel by commit ancestry.
Exploitation context
The CVSS vector describes local, low-complexity access requiring low privileges and no user interaction. The supplied sources document failures during ordinary camera streaming, not malicious exploitation. This CVE is not listed as KEV in the bundle, and no cited source establishes active exploitation.
Researcher notes
The strongest evidence is a stream teardown state-management flaw: use_count tracks user-space opens, not active streams. The source reports WARN splats, unreleased videobuf2 buffers, and persistent EBUSY behavior. No CWE is assigned. Confidentiality and integrity impacts implied by CVSS are not independently demonstrated in the supplied narrative.
Mitigation direction
- Install a vendor kernel containing the applicable stable fix commit.
- Verify backported vendor kernels by commit presence, not version number alone.
- If no update is available, request platform-specific guidance from the device or kernel vendor.
- Avoid deploying affected kernels on CAMSS-dependent devices until remediation is confirmed.
Validation and detection
- Inventory Linux versions and devices using Qualcomm CAMSS camera hardware.
- Check kernel source or package metadata for the applicable stable fix commit.
- Review kernel logs for videobuf2 queue-cancel warnings and active-buffer messages.
- Test repeated camera start-stop cycles and confirm subsequent starts do not return EBUSY.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2024-50175 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9CVE reference, Linux
- https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3CVE reference, Linux
- https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412deeCVE reference, Linux
- https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.