<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T21:22:37.251494+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2022-48987</id>
    <title>CVE-2022-48987 — media: v4l2-dv-timings.c: fix too strict blanking sanity checks</title>
    <updated>2026-09-29T21:22:37.276809+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>media: v4l2-dv-timings.c: fix too strict blanking sanity checks</p>
<p>Sanity checks were added to verify the v4l2_bt_timings blanking fields
in order to avoid integer overflows when userspace passes weird values.</p>
<p>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.</p>
<p>And that can fail with these checks.</p>
<p>So instead set a maximum for the total horizontal and vertical
blanking and check that each field remains below that.</p>
<p>That is still sufficient to avoid integer overflows, but it also
allows for more flexibility in how userspace fills in these fields.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-48987"/>
  </entry>
</feed>
