CVE-2026-68209

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 — 3 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: sun4i-csi: Return queued buffers on start_streaming() failure

The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak.

sun4i_csi_start_streaming() returned -EINVAL when no matching CSI format could be found, before any setup (scratch buffer allocation, pipeline start) had been performed. The remaining error paths already converge on the err_clear_dma_queue label, which calls return_all_buffers(..., VB2_BUF_STATE_QUEUED) under csi->qlock. Jump to that label directly: the intermediate err_disable_device / err_disable_pipeline / err_free_scratch_buffer labels are skipped, which is correct because nothing they would undo has happened yet.

This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure").

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: sun4i-csi: Return queued buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: sun4i-csi: Return queued buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: sun4i-csi: Return queued buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: sun4i-csi: Return queued buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/668face37fdb6b6900645dc8777195498541c9a7
generic

media: sun4i-csi: Return queued buffers on start_streaming() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4872161e6fbe4e1783daea8bff79caddfae0fb82

Vendor Advisories for CVE-2026-68209(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 33× in last 7d / 45× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 18:48 UTCGHSA enrichment
  3. 2026-08-20 06:07 UTCGHSA enrichment
  4. 2026-08-19 17:25 UTCEG score recompute
  5. 2026-08-19 17:25 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:55 UTCEG score recompute
  8. 2026-08-19 16:55 UTCGHSA enrichment
  9. 2026-08-19 09:28 UTCGHSA enrichment
  10. 2026-08-18 20:45 UTCEG score recompute
  11. 2026-08-18 20:45 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 08:03 UTCGHSA enrichment
  15. 2026-08-17 19:20 UTCEG score recompute
  16. 2026-08-17 19:20 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 05:38 UTCEG score recompute
  19. 2026-08-17 05:38 UTCGHSA enrichment
  20. 2026-08-17 05:09 UTCEG score recompute
  21. 2026-08-17 05:09 UTCGHSA enrichment
  22. 2026-08-17 03:37 UTCEG score recompute
  23. 2026-08-17 03:37 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCGHSA enrichment
Show 20 more
  1. 2026-08-16 02:15 UTCEG score recompute
  2. 2026-08-16 02:15 UTCGHSA enrichment
  3. 2026-08-15 13:34 UTCEG score recompute
  4. 2026-08-15 13:34 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-15 00:52 UTCGHSA enrichment
  7. 2026-08-14 12:10 UTCEG score recompute
  8. 2026-08-14 12:10 UTCGHSA enrichment
  9. 2026-08-13 23:29 UTCEG score recompute
  10. 2026-08-13 23:29 UTCGHSA enrichment
  11. 2026-08-13 22:44 UTCEG score recompute▲ 7.80
  12. 2026-08-13 22:44 UTCGHSA enrichment
  13. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 12:55 UTCEG score recompute
  16. 2026-08-13 12:55 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:20 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68209?
CVE-2026-68209 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: media: sun4i-csi: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling startstreaming(). If startstreaming() returns an error without first returning those…
When was CVE-2026-68209 disclosed?
CVE-2026-68209 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-68209 actively exploited?
CVE-2026-68209 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-68209?
CVE-2026-68209 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68209?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68209, 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-68209

Explore →

Is Your Infrastructure Affected by CVE-2026-68209?

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

Start Free Scan →Browse All CVEs