Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2024-50175— media: qcom: camss: Remove use_count guard in stop_streaming

EPSS 0.02% · P5
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-50175

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
media: qcom: camss: Remove use_count guard in stop_streaming
Source: NVD (National Vulnerability Database)
Vulnerability 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")
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于对use_count的错误使用导致竞争条件。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 89013969e23247661f0514c77f26d60fa083216c ~ c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 -
LinuxLinux 6.4 -

II. Public POCs for CVE-2024-50175

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-50175

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-11-08 · 38 CVEs total

CVE-2024-50203bpf, arm64: Fix address emission with tag-based KASAN enabled
CVE-2024-50194arm64: probes: Fix uprobes for big-endian kernels
CVE-2024-50195posix-clock: Fix missing timespec64 check in pc_clock_settime()
CVE-2024-50196pinctrl: ocelot: fix system hang on level based interrupts
CVE-2024-50197pinctrl: intel: platform: fix error path in device_for_each_child_node()
CVE-2024-50198iio: light: veml6030: fix IIO device retrieval from embedded device
CVE-2024-50199mm/swapfile: skip HugeTLB pages for unuse_vma
CVE-2024-50200maple_tree: correct tree corruption on spanning store
CVE-2024-50201drm/radeon: Fix encoder->possible_clones
CVE-2024-50202nilfs2: propagate directory read errors from nilfs_find_entry()
CVE-2024-50193x86/entry_32: Clear CPU buffers after register restore in NMI return
CVE-2024-50204fs: don't try and remove empty rbtree node
CVE-2024-50205ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size()
CVE-2024-50206net: ethernet: mtk_eth_soc: fix memory corruption during fq dma init
CVE-2024-50207ring-buffer: Fix reader locking when changing the sub buffer order
CVE-2024-50209RDMA/bnxt_re: Add a check for memory allocation
CVE-2024-50208RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages
CVE-2024-50210posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime()
CVE-2024-50211udf: refactor inode_bmap() to handle error
CVE-2024-50184virtio_pmem: Check device status before requesting flush

Showing top 20 of 38 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2024-50175

No comments yet


Leave a comment