CVE-2026-68204

Received Received - Intake

Vivid Kernel Media Format Capability Validation Flaw

Publication date: 2026-08-10

Last updated on: 2026-08-19

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2_is_busy() when toggling caps The vivid_update_format_cap/out() functions must only be called if the capture/output queue are not busy. But for the controls that select the CROP/COMPOSE/SCALE capability that is not checked. Only when streaming starts will they be set to 'grabbed' and it is impossible to change the control, but between REQBUFS and STREAMON you are still allowed to set these controls. Since vivid_update_format_cap/out will change the format, this can cause unexpected results. Besides adding these checks, also add a WARN_ON in vivid_update_format_cap/out() if the queue is busy. I'm 90% certain that this is the cause of this syzbot bug: https://syzkaller.appspot.com/bug?extid=dac8f5eaa46837e97b89 But since we never have reproducers, it is hard to be certain. In any case, these checks are needed regardless.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-10

Last Modified

2026-08-19

Generated

2026-08-30

AI Q&A

2026-08-10

EPSS Evaluated

2026-08-29

NVD

CVE-2026-68204

EUVD

EUVD-2026-55305

Affected Vendors & Products

Vendor	Product	Version / Range
linux_kernel	media_vivid	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's media subsystem, specifically in the vivid driver. It involves improper handling of format updates for capture/output queues when toggling capabilities like CROP, COMPOSE, or SCALE. The vivid_update_format_cap/out() functions can change formats even when queues are busy, leading to unexpected behavior. Checks for vb2_is_busy() were missing, allowing unsafe format changes between REQBUFS and STREAMON operations.

Detection Guidance

This vulnerability is specific to the Linux kernel's vivid media driver and cannot be detected via standard network or system commands. It requires kernel-level inspection for issues in the vivid driver's format handling during queue operations.

Impact Analysis

This vulnerability could cause system instability or crashes in systems using the vivid driver, particularly those handling media operations. It may lead to unexpected format changes during media streaming, potentially disrupting video capture or output functionality. Systems relying on media processing could experience data corruption or performance issues.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a media device driver issue in the Linux kernel that could cause unexpected format changes but does not involve data exposure or privacy violations typical of compliance concerns.

Mitigation Strategies

Apply the latest Linux kernel patches that include the fix for this vivid driver vulnerability. Monitor kernel security advisories and update your system to a patched kernel version as soon as possible.

Hi! I’m here to help you understand CVE-2026-68204. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70