CVE-2026-68204

High

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.

SeverityHigh
CVSS7.8
Exploit probability—
ProductLinux
PublishedAug 10, 2026
First seenAug 10, 2026

How to fix

Update
  • Linux Linux0a820f03727b509b887f3216a574062948761f34, bbc96bc75de0fcd9bb6ac48798b206e3b09ec865, 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de, a9cd0e8fb0b21faaa71199d9d3feb305c18ff576, abaec6747304581f8d4a9936352fa10e13325f07, 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf, daf2d92669b4a659d805d88d811161c70cd325ee, c2d1a2130c93f6d758af58590b86b2254c7a1dec or later

Affected products

ProductAffected versionsFixed in
Linux Linux73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < 0a820f03727b509b887f3216a574062948761f34, 73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < bbc96bc75de0fcd9bb6ac48798b206e3b09ec865, 73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de, 73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < a9cd0e8fb0b21faaa71199d9d3feb305c18ff576, 73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < abaec6747304581f8d4a9936352fa10e13325f07, 73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf, 73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < daf2d92669b4a659d805d88d811161c70cd325ee, 73c3f48230cda01402ae189b05d56f1f7e0d53c9 ≤ v < c2d1a2130c93f6d758af58590b86b2254c7a1dec, 3.180a820f03727b509b887f3216a574062948761f34, bbc96bc75de0fcd9bb6ac48798b206e3b09ec865, 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de, a9cd0e8fb0b21faaa71199d9d3feb305c18ff576, abaec6747304581f8d4a9936352fa10e13325f07, 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf, daf2d92669b4a659d805d88d811161c70cd325ee, c2d1a2130c93f6d758af58590b86b2254c7a1dec

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.