Answer in brief
CVE-2026-68204 records a Unknown severity vulnerability in media: vivid: check for vb2_is_busy() when toggling caps. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <a9cd0e8fb0b21faaa71199d9d3feb305c18ff576 || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <abaec6747304581f8d4a9936352fa10e13325f07 || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <492c97cb50feaa60ccd7792d3d6b904ed8ec61bf || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <daf2d92669b4a659d805d88d811161c70cd325ee || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <c2d1a2130c93f6d758af58590b86b2254c7a1dec | a9cd0e8fb0b21faaa71199d9d3feb305c18ff576, abaec6747304581f8d4a9936352fa10e13325f07, 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf, daf2d92669b4a659d805d88d811161c70cd325ee, c2d1a2130c93f6d758af58590b86b2254c7a1dec |
| Linux/Linuxgeneric | 3.18 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68204 records a Unknown severity vulnerability in media: vivid: check for vb2_is_busy() when toggling caps. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <a9cd0e8fb0b21faaa71199d9d3feb305c18ff576 || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <abaec6747304581f8d4a9936352fa10e13325f07 || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <492c97cb50feaa60ccd7792d3d6b904ed8ec61bf || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <daf2d92669b4a659d805d88d811161c70cd325ee || >=73c3f48230cda01402ae189b05d56f1f7e0d53c9 <c2d1a2130c93f6d758af58590b86b2254c7a1dec | a9cd0e8fb0b21faaa71199d9d3feb305c18ff576, abaec6747304581f8d4a9936352fa10e13325f07, 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf, daf2d92669b4a659d805d88d811161c70cd325ee, c2d1a2130c93f6d758af58590b86b2254c7a1dec |
| Linux/Linuxgeneric | 3.18 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.