CVE-2026-68204

media: vivid: check for vb2_is_busy() when toggling caps

HIGH
7.8
CVSS Score
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.18 ≤ v < 5.10.2653.18 ≤ v < 5.15.2163.18 ≤ v < 6.1.1833.18 ≤ v < 6.12.1013.18 ≤ v < 6.18.423.18 ≤ v < 6.6.1483.18 ≤ v < 7.1.63.18 ≤ v < 7.23.1873c3f48230cda01402ae189b05d56f1f7e0d53c9
Vendor states this is fixed in 0a820f03727b509b887f3216a574062948761f34 (fixed)
Vendor states this is fixed in 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf (fixed)
Vendor states this is fixed in 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de (fixed)
Vendor states this is fixed in a9cd0e8fb0b21faaa71199d9d3feb305c18ff576 (fixed)
Vendor states this is fixed in abaec6747304581f8d4a9936352fa10e13325f07 (fixed)
Vendor states this is fixed in bbc96bc75de0fcd9bb6ac48798b206e3b09ec865 (fixed)
Vendor states this is fixed in c2d1a2130c93f6d758af58590b86b2254c7a1dec (fixed)
Vendor states this is fixed in daf2d92669b4a659d805d88d811161c70cd325ee (fixed)
Vendor states this is fixed in 3.18 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card