CVE-2026-68206
CVE CVE-2026-68206EUVD EUVD-2026-55307Published 2026-08-10T12:00:25.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux d395a78db9eabd12633b39e05c80e803543b6590 <b01df98a6669d2b67d8aed816021b327fd905998; patch: 6.6.148; patch: 6.18.42; d395a78db9eabd12633b39e05c80e803543b6590 <dbaf0e0023e2f9332c5164822def7f80b7d2c5ef; d395a78db9eabd12633b39e05c80e803543b6590 <3068ab802fc98b121dcb451e1f7f4d338ffc7a19; d395a78db9eabd12633b39e05c80e803543b6590 <9a998cc1c348769262d433acb7d238c5fac4b2e0; patch: 7.1.6; 5.14; patch: 0; patch: 7.2-rc1; patch: 6.12.101; d395a78db9eabd12633b39e05c80e803543b6590 <afbe4bc252d90a6f8fad869b06d5430f615f22f9
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.