linux-cve-announce - CVE-2022-50757: media: camss: Clean up received buffers on failed start of streaming

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025122454-CVE-2022-50757-15f0@gregkh>
Date: Wed, 24 Dec 2025 14:06:08 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50757: media: camss: Clean up received buffers on failed start of streaming

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

media: camss: Clean up received buffers on failed start of streaming

It is required to return the received buffers, if streaming can not be
started. For instance media_pipeline_start() may fail with EPIPE, if
a link validation between entities is not passed, and in such a case
a user gets a kernel warning:

  WARNING: CPU: 1 PID: 520 at drivers/media/common/videobuf2/videobuf2-core.c:1592 vb2_start_streaming+0xec/0x160
  <snip>
  Call trace:
   vb2_start_streaming+0xec/0x160
   vb2_core_streamon+0x9c/0x1a0
   vb2_ioctl_streamon+0x68/0xbc
   v4l_streamon+0x30/0x3c
   __video_do_ioctl+0x184/0x3e0
   video_usercopy+0x37c/0x7b0
   video_ioctl2+0x24/0x40
   v4l2_ioctl+0x4c/0x70

The fix is to correct the error path in video_start_streaming() of camss.

The Linux kernel CVE team has assigned CVE-2022-50757 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 4.14.303 with commit 75954cde8a5ca84003b24b6bf83197240935bd74
	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 4.19.270 with commit 04c734c716a97f1493b1edac41316aaed1d2a9d9
	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 5.4.229 with commit fe443b3fe36cd23d4f5dc6d825d34322e7c89f0c
	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 5.10.163 with commit 3d5cab726e3b370fea1b6e67183f0e13c409ce5c
	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 5.15.86 with commit d1c44928bb3ca0ec88e7ad5937a2a26a259aede6
	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 6.0.16 with commit f05326a440dc31b91b688b2f3f15b7347894a50b
	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 6.1.2 with commit 24df4fa3e795fb4b15fd4d3c036596e0978d265a
	Issue introduced in 4.14 with commit 0ac2586c410fe00d58dd09bf270a22f25d5287b8 and fixed in 6.2 with commit c8f3582345e6a69da65ab588f7c4c2d1685b0e80

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-50757
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/media/platform/qcom/camss/camss-video.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/75954cde8a5ca84003b24b6bf83197240935bd74
	https://git.kernel.org/stable/c/04c734c716a97f1493b1edac41316aaed1d2a9d9
	https://git.kernel.org/stable/c/fe443b3fe36cd23d4f5dc6d825d34322e7c89f0c
	https://git.kernel.org/stable/c/3d5cab726e3b370fea1b6e67183f0e13c409ce5c
	https://git.kernel.org/stable/c/d1c44928bb3ca0ec88e7ad5937a2a26a259aede6
	https://git.kernel.org/stable/c/f05326a440dc31b91b688b2f3f15b7347894a50b
	https://git.kernel.org/stable/c/24df4fa3e795fb4b15fd4d3c036596e0978d265a
	https://git.kernel.org/stable/c/c8f3582345e6a69da65ab588f7c4c2d1685b0e80