# CVE-2024-50175: linux: In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: Remove use_count guard in st... CVE-2024-50175 is fixed in 26 products on 1 platform, first by DEBIAN-CVE-2024-50175, released November 8, 2024. It is not reported as exploited. Patch Radar priority: Routine. - Web page: https://patchblox.com/security/cve/CVE-2024-50175 - Priority: Routine - CVSS: 5.5 (medium) - EPSS: 0.0023 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Nov 8, 2024 ## Description 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") ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | dtb-aarch64 opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-64kb opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-64kb sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-azure opensuse-leap 15.6 | 6.4.0-150600.8.20.1 | [SUSE-SU-2024:4316-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4316-1.md) | Dec 13, 2024 | | Linux | kernel-azure sles 15.6 | 6.4.0-150600.8.20.1 | [SUSE-SU-2024:4316-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4316-1.md) | Dec 13, 2024 | | Linux | kernel-coco sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-coco_debug sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-debug opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default-base opensuse-leap 15.6 | 6.4.0-150600.23.30.1.150600.12.12.6 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default-base sles 15.6 | 6.4.0-150600.23.30.1.150600.12.12.6 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-docs opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-docs sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-kvmsmall opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-livepatch-SLE15-SP6-RT_Update_6 sles 15.6 | 1-150600.1.3.1 | [SUSE-SU-2024:4314-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4314-1.md) | Dec 13, 2024 | | Linux | kernel-livepatch-SLE15-SP6_Update_6 sles 15.6 | 1-150600.13.3.5 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-obs-build opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-obs-build sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-obs-qa opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-rt opensuse-leap 15.6 | 6.4.0-150600.10.20.1 | [SUSE-SU-2024:4314-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4314-1.md) | Dec 13, 2024 | | Linux | kernel-rt_debug opensuse-leap 15.6 | 6.4.0-150600.10.20.1 | [SUSE-SU-2024:4314-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4314-1.md) | Dec 13, 2024 | | Linux | kernel-source opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-source sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-source-azure opensuse-leap 15.6 | 6.4.0-150600.8.20.1 | [SUSE-SU-2024:4316-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4316-1.md) | Dec 13, 2024 | | Linux | kernel-source-azure sles 15.6 | 6.4.0-150600.8.20.1 | [SUSE-SU-2024:4316-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4316-1.md) | Dec 13, 2024 | | Linux | kernel-source-coco sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-source-rt opensuse-leap 15.6 | 6.4.0-150600.10.20.1 | [SUSE-SU-2024:4314-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4314-1.md) | Dec 13, 2024 | | Linux | kernel-syms opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-syms sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-syms-azure opensuse-leap 15.6 | 6.4.0-150600.8.20.1 | [SUSE-SU-2024:4316-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4316-1.md) | Dec 13, 2024 | | Linux | kernel-syms-azure sles 15.6 | 6.4.0-150600.8.20.1 | [SUSE-SU-2024:4316-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4316-1.md) | Dec 13, 2024 | | Linux | kernel-syms-coco sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-syms-rt opensuse-leap 15.6 | 6.4.0-150600.10.20.1 | [SUSE-SU-2024:4314-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4314-1.md) | Dec 13, 2024 | | Linux | kernel-zfcpdump opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-zfcpdump sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | linux Debian 13.5 (trixie) | 6.11.4-1 | [DEBIAN-CVE-2024-50175](https://patchblox.com/security/data/fix/linux/debian-cve-2024-50175.md) | Nov 8, 2024 | | Linux | linux Debian 14 | 6.11.4-1 | [DEBIAN-CVE-2024-50175](https://patchblox.com/security/data/fix/linux/debian-cve-2024-50175.md) | Nov 8, 2024 | --- Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.