LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel camera driver bug in the camss media path. If camera streaming fails to start, buffers may not be cleaned up correctly, causing a kernel warning. Public sources do not provide a CVSS score, confirmed security impact, or exploitation evidence.

Executive priority

Handle through normal kernel maintenance unless affected devices are business-critical or exposed to untrusted local users. The public record lacks exploitation evidence and severity scoring, but kernel fixes should still be incorporated into standard patch cycles.

Technical view

The issue is in camss video_start_streaming(). When media_pipeline_start() fails, for example with EPIPE during link validation, received videobuf2 buffers are not returned. The upstream fix corrects that error path so buffers are cleaned up on failed streaming start.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the camss media driver and accessible camera/video interfaces. The CVE record lists affected stable ranges through 6.2, but organizations should verify downstream vendor backports.

Exploitation context

No CISA KEV listing or cited source indicates active exploitation. The described trigger is local camera streaming through V4L2 paths, not a network-facing condition. Public sources show a kernel warning scenario, but not a complete impact assessment.

Researcher notes

The record describes a cleanup bug, not a memory-corruption primitive. Key unknowns are downstream affected configurations, security impact beyond warning/buffer handling, and whether device vendors backported the fix. Validate against actual kernel source, not version numbers alone.

Mitigation direction

  • Apply a Linux kernel update containing the referenced stable fix.
  • Check distribution or device-vendor advisories for backported kernel packages.
  • Prioritize systems using camss camera/media functionality.
  • Limit untrusted local access to camera devices where practical.

Validation and detection

  • Inventory Linux kernel versions on camera-enabled devices.
  • Determine whether the camss media driver is present and used.
  • Compare installed kernels against vendor-fixed builds or referenced stable commits.
  • Review kernel logs for vb2_start_streaming warnings after failed camera streaming.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2022-50757 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0ac2586c410fe00d58dd09bf270a22f25d5287b8, 0ac2586c410fe00d58dd09bf270a22f25d5287b8, 0ac2586c410fe00d58dd09bf270a22f25d5287b8, 0ac2586c410fe00d58dd09bf270a22f25d5287b8, 0ac2586c410fe00d58dd09bf270a22f25d5287b8, 0ac2586c410fe00d58dd09bf270a22f25d5287b8, 0ac2586c410fe00d58dd09bf270a22f25d5287b8, 0ac2586c410fe00d58dd09bf270a22f25d5287b8unaffected
LinuxLinux4.14, 0, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.