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

> A local attacker can trigger a kernel warning and potential denial of service by failing to start streaming in the CamSS media driver.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50757, GHSA-g5hv-6pvx-45rj, UBUNTU-CVE-2022-50757

## What is CVE-2022-50757?

CVE-2022-50757 is a high-severity denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2022-50757?


## How do I fix CVE-2022-50757?

Apply the vendor's patch.

## Is CVE-2022-50757 being exploited?

There is no known exploitation of CVE-2022-50757 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50757 and fix it if it is affected.

What it is: CVE-2022-50757 is a high-severity denial of service vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50757 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50757/ (Markdown: https://insights.sbomify.com/CVE-2022-50757/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50757
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50757
- OSV: https://osv.dev/vulnerability/CVE-2022-50757

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50757/
Summaries are generated and may contain mistakes; the official description above is the record.