CVE-2022-48987

media: v4l2-dv-timings.c: fix too strict blanking sanity checks

MEDIUM

5.5

CVSS Score

Published: October 21, 2024 at 08:06 PM UTC

Updated: June 17, 2026 at 05:16 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-dv-timings.c: fix too strict blanking sanity checks Sanity checks were added to verify the v4l2_bt_timings blanking fields in order to avoid integer overflows when userspace passes weird values. But that assumed that userspace would correctly fill in the front porch, backporch and sync values, but sometimes all you know is the total blanking, which is then assigned to just one of these fields. And that can fail with these checks. So instead set a maximum for the total horizontal and vertical blanking and check that each field remains below that. That is still sufficient to avoid integer overflows, but it also allows for more flexibility in how userspace fills in these fields.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.14.298 ≤ v < 4.14.3024.19.264 ≤ v < 4.19.2694.9.332 ≤ v < 4.9.3365.10.153 ≤ v < 5.10.1595.15.77 ≤ v < 5.15.835.4.223 ≤ v < 5.4.2275.4.226 ≤ v < 5.4.2276.0.7 ≤ v < 6.0.1315ded23db134da975b49ea99770de0346c193b243d43b2b8a3cdadd6cef9ac8ef5d156b6214a01c84.14.298 4.19.264 4.9.332491c0959f01d87bcbd5a1498bc70e0a3382c65a84b6d66a45ed34a15721cb9e11492fa1a24bc83df5.10.153 5.15.77 5.4.223 6.0.7683015ae163481457a16fad2317af66360dc47629cf9211635b68e8e0c8cb88d43ca7dc83e4632aab4a3a01762ae072c7f6ff2ff53b5019761288346dc7276c3f6ca008be1faf531f84b49906c9bcf7f

Vendor states this is fixed in 0d73b49c4037199472b29574ae21c21aef493971 (fixed)

Vendor states this is fixed in 2572ab14b73aa45b6ae7e4c089ccf119fed5cf89 (fixed)

Vendor states this is fixed in 32f01f0306a98629508f84d7ef0d1d037bc274a2 (fixed)

Vendor states this is fixed in 4afc77068e36cee45b39d4fdc7513de26980f72c (fixed)

Vendor states this is fixed in 5eef2141776da02772c44ec406d6871a790761ee (fixed)

Vendor states this is fixed in 6fb8bc29bfa80707994a63cc97e2f9920e0b0608 (fixed)

Vendor states this is fixed in a2b56627c0d13009e02f6f2c0206c0451ed19a0e (fixed)

Vendor states this is fixed in d3d14cdf1c7ae2caa3e999bae95ba99e955fb7c3 (fixed)

Affected range stops below 4.14.302, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.19.269, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.9.336, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.10.159, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.15.83, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.227, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.0.13, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references