<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 07:44:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49478 — media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49478</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init&lt;/p&gt;
&lt;p&gt;Syzbot reported that -1 is used as array index. The problem was in
missing validation check.&lt;/p&gt;
&lt;p&gt;hdw-&amp;gt;unit_number is initialized with -1 and then if init table walk fails
this value remains unchanged. Since code blindly uses this member for
array indexing adding sanity check is the easiest fix for that.&lt;/p&gt;
&lt;p&gt;hdw-&amp;gt;workpoll initialization moved upper to prevent warning in
__flush_work.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init&lt;/p&gt;
&lt;p&gt;Syzbot reported that -1 is used as array index. The problem was in
missing validation check.&lt;/p&gt;
&lt;p&gt;hdw-&amp;gt;unit_number is initialized with -1 and then if init table walk fails
this value remains unchanged. Since code blindly uses this member for
array indexing adding sanity check is the easiest fix for that.&lt;/p&gt;
&lt;p&gt;hdw-&amp;gt;workpoll initialization moved upper to prevent warning in
__flush_work.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49478</guid>
    </item>
  </channel>
</rss>
