CVE-2026-68106
CVE-2026-68106 is a high-severity vulnerability with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-369.
Key facts
- Severity: High (CVSS 3.x base score 7.8)
- EPSS exploit prediction: 0% (3rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-369
- Published:
- Last modified:
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix division by zero with invalid uvd dimensions When width or height is less than 16, width_in_mb or height_in_mb becomes 0, leading to fs_in_mb being 0. This causes a division by zero when calculating num_dpb_buffer in H264 and H264 Perf decode paths. Add validation to reject frames with width < 16 or height < 16 before performing any calculations that depend on these values. V2: Format change - move up all vaiable definitions. V3: Use warn_once to avoid spam. (cherry picked from commit 3e41d26c70b0a459d041cc19482a226c4b7423cb)
Frequently asked questions
- What is CVE-2026-68106?
- In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix division by zero with invalid uvd dimensions When width or height is less than 16, width_in_mb or height_in_mb becomes 0, leading to fs_in_mb being 0. This causes a division by zero when calculating num_dpb_buffer in H264 and H264 Perf decode paths. Add validation to reject frames with width < 16 or height < 16 before performing any calculations that depend on these values. V2: Format change - move up all vaiable definitions. V3: Use warn_once to avoid spam. (cherry picked from commit 3e41d26c70b0a459d041cc19482a226c4b7423cb)
- How severe is CVE-2026-68106?
- CVE-2026-68106 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-68106 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-68106?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-68106 published?
- CVE-2026-68106 was published on 2026-08-10 and last updated on 2026-10-19.
References
- https://git.kernel.org/stable/c/004d0453cfef16f056cb7b8bc04f69f19cf9df32
- https://git.kernel.org/stable/c/00ee64910ecf748cc15b23bbcbea472c203ec1e8
- https://git.kernel.org/stable/c/0c01c811be47e6b146552dd59bfedbea8f09b8f4
- https://git.kernel.org/stable/c/52f9a588296432accf2982f7d258192a37562f4f
- https://git.kernel.org/stable/c/81c9b4921f62d1642b9d775524ae9240e521a5ed
- https://git.kernel.org/stable/c/a00946b5ab7c25da5685ca9c58f50ff6f43c0fdf
- https://git.kernel.org/stable/c/be725ab23aa45c11a5afef3e2a9f6d8c084ae5dc
- https://git.kernel.org/stable/c/ffb33d466a68cea3e8a3dbed04d79037a3cbabd1
Other CWE-369 (Divide By Zero) vulnerabilities
- CVE-2021-32494 — Critical (CVSS 10.0): Radare2 has a division by zero vulnerability in Mach-O parser's rebase_buffer function. This allow attackers to create…
- CVE-2024-57932 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: gve: guard XDP xmit NDO on existence of xdp…
- CVE-2017-11720 — Critical (CVSS 9.8): There is a division-by-zero vulnerability in LAME 3.99.5, caused by a malformed input file.
- CVE-2020-20892 — High (CVSS 8.8): An issue was discovered in function filter_frame in libavfilter/vf_lenscorrection.c in Ffmpeg 4.2.1, allows attackers…
- CVE-2026-37232 — High (CVSS 8.6): An issue was discovered in OpenAirInterface5G 2.4.0 (nr-softmodem) in the E2SM-KPM RAN Function's PRB utilization…
- CVE-2024-26945 — High (CVSS 8.4): In the Linux kernel, the following vulnerability has been resolved: crypto: iaa - Fix nr_cpus < nr_iaa case If…