CVE-2026-68204

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

media: vivid: check for vb2_is_busy() when toggling caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/daf2d92669b4a659d805d88d811161c70cd325ee
generic

media: vivid: check for vb2_is_busy() when toggling caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2d1a2130c93f6d758af58590b86b2254c7a1dec
generic

media: vivid: check for vb2_is_busy() when toggling caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/abaec6747304581f8d4a9936352fa10e13325f07
generic

media: vivid: check for vb2_is_busy() when toggling caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a9cd0e8fb0b21faaa71199d9d3feb305c18ff576
generic

media: vivid: check for vb2_is_busy() when toggling caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/492c97cb50feaa60ccd7792d3d6b904ed8ec61bf

Vendor Advisories for CVE-2026-68204(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 37× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 03:50 UTCEG score recompute
  2. 2026-08-21 03:50 UTCVendor advisory
  3. 2026-08-21 03:50 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 16:22 UTCGHSA enrichment
  6. 2026-08-20 04:54 UTCGHSA enrichment
  7. 2026-08-19 17:25 UTCEG score recompute
  8. 2026-08-19 17:25 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 16:55 UTCEG score recompute
  11. 2026-08-19 16:55 UTCGHSA enrichment
  12. 2026-08-19 16:21 UTCGHSA enrichment
  13. 2026-08-19 04:53 UTCGHSA enrichment
  14. 2026-08-18 17:25 UTCEG score recompute
  15. 2026-08-18 17:25 UTCGHSA enrichment
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 13:49 UTCEPSS rescore
  18. 2026-08-18 04:36 UTCGHSA enrichment
  19. 2026-08-17 17:07 UTCEG score recompute
  20. 2026-08-17 17:07 UTCGHSA enrichment
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 05:38 UTCEG score recompute
  23. 2026-08-17 05:38 UTCGHSA enrichment
  24. 2026-08-17 05:09 UTCEG score recompute
  25. 2026-08-17 05:09 UTCGHSA enrichment
Show 24 more
  1. 2026-08-16 20:19 UTCEG score recompute
  2. 2026-08-16 20:19 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 08:50 UTCEG score recompute
  5. 2026-08-16 08:50 UTCGHSA enrichment
  6. 2026-08-15 21:22 UTCGHSA enrichment
  7. 2026-08-15 09:54 UTCEG score recompute
  8. 2026-08-15 09:54 UTCGHSA enrichment
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 22:25 UTCGHSA enrichment
  11. 2026-08-14 10:57 UTCEG score recompute
  12. 2026-08-14 10:57 UTCGHSA enrichment
  13. 2026-08-13 23:29 UTCEG score recompute
  14. 2026-08-13 23:29 UTCGHSA enrichment
  15. 2026-08-13 22:45 UTCEG score recompute▲ 7.80
  16. 2026-08-13 22:45 UTCGHSA enrichment
  17. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 12:23 UTCEG score recompute
  20. 2026-08-13 12:23 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-10 13:24 UTCNVD update
  23. 2026-08-10 12:20 UTCEG score recompute
  24. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-68204?
CVE-2026-68204 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: media: vivid: check for vb2isbusy() when toggling caps The vividupdateformat_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…
When was CVE-2026-68204 disclosed?
CVE-2026-68204 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68204 actively exploited?
CVE-2026-68204 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68204?
CVE-2026-68204 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68204?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68204, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68204

Explore →

Is Your Infrastructure Affected by CVE-2026-68204?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs