CVE-2026-68204: media: vivid: check for vb2_is_busy() when toggling caps
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0a820f03727b509b887f3216a574062948761f34, 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf, 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0a820f03727b509b887f3216a574062948761f34, 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf, 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.18affected
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before 0a820f03727b509b887f3216a574062948761f34affected · git
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before bbc96bc75de0fcd9bb6ac48798b206e3b09ec865affected · git
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89deaffected · git
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before a9cd0e8fb0b21faaa71199d9d3feb305c18ff576affected · git
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before abaec6747304581f8d4a9936352fa10e13325f07affected · git
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before 492c97cb50feaa60ccd7792d3d6b904ed8ec61bfaffected · git
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before daf2d92669b4a659d805d88d811161c70cd325eeaffected · git
- 73c3f48230cda01402ae189b05d56f1f7e0d53c9 and later · before c2d1a2130c93f6d758af58590b86b2254c7a1decaffected · git
- before 3.18not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68195Aug 10, 2026 · wifi: mt76: mt7615: drop TXRX_NOTIFY on non-mmio buses0Monitor
- ← EarlierCVE-2026-68196Aug 10, 2026 · wifi: wilc1000: validate assoc response length before subtracting header33Monitor
- Later →CVE-2026-68207Aug 10, 2026 · media: ti: vpe: unwind v4l2 device registration on probe error0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0a820f03727b509b887f3216a574062948761f34 | Vendor (CNA) |
| Linux Linux | 492c97cb50feaa60ccd7792d3d6b904ed8ec61bf | Vendor (CNA) |
| Linux Linux | 6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de | Vendor (CNA) |
| Linux Linux | a9cd0e8fb0b21faaa71199d9d3feb305c18ff576 | Vendor (CNA) |
| Linux Linux | abaec6747304581f8d4a9936352fa10e13325f07 | Vendor (CNA) |
| Linux Linux | bbc96bc75de0fcd9bb6ac48798b206e3b09ec865 | Vendor (CNA) |
| Linux Linux | c2d1a2130c93f6d758af58590b86b2254c7a1dec | Vendor (CNA) |
| Linux Linux | daf2d92669b4a659d805d88d811161c70cd325ee | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/492c97cb50feaa60ccd7792d3d6b904ed8ec61bf
- git.kernel.org/stable/c/6a5bc8aea111ccbca71ef2b9c868d5c81f2e89de
- git.kernel.org/stable/c/a9cd0e8fb0b21faaa71199d9d3feb305c18ff576
- git.kernel.org/stable/c/abaec6747304581f8d4a9936352fa10e13325f07
- git.kernel.org/stable/c/bbc96bc75de0fcd9bb6ac48798b206e3b09ec865
- git.kernel.org/stable/c/c2d1a2130c93f6d758af58590b86b2254c7a1dec
- git.kernel.org/stable/c/daf2d92669b4a659d805d88d811161c70cd325ee
Vendor advisories and official records. Exploit/PoC links are deliberately left out.