Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68206media: v4l2-ctrls: validate HEVC active reference counts

Description

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-ctrls: validate HEVC active reference counts HEVC slice parameters are shared stateless V4L2 controls, but the common validation path does not verify the active L0/L1 reference counts before driver-specific code consumes them. The original report came from Cedrus, but the active count bounds are not Cedrus-specific. Validate them in the common HEVC slice control path so stateless HEVC drivers get the same basic guarantees as soon as the control is queued. Do not reject ref_idx_l0/ref_idx_l1 entries here. Existing userspace may use out-of-range sentinel values such as 0xff for missing references, and some hardware can use that information for concealment. Keep this common check limited to the active reference counts.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68206, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected d395a78db9eabd12633b39e05c80e803543b6590 – < 3299c3905f3fb439ebd892658b87bc76c93ae116
    • affected d395a78db9eabd12633b39e05c80e803543b6590 – < 9a998cc1c348769262d433acb7d238c5fac4b2e0
    • affected d395a78db9eabd12633b39e05c80e803543b6590 – < dbaf0e0023e2f9332c5164822def7f80b7d2c5ef
    • affected d395a78db9eabd12633b39e05c80e803543b6590 – < 3068ab802fc98b121dcb451e1f7f4d338ffc7a19
    • affected d395a78db9eabd12633b39e05c80e803543b6590 – < b01df98a6669d2b67d8aed816021b327fd905998
    • affected d395a78db9eabd12633b39e05c80e803543b6590 – < afbe4bc252d90a6f8fad869b06d5430f615f22f9
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68206 badge
[![CVE-2026-68206](https://cveledger.app/badge/CVE-2026-68206.svg)](https://cveledger.app/cve/CVE-2026-68206)

Record last updated .