<?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>Mon, 05 Oct 2026 16:38:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49051 — net: usb: aqc111: Fix out-of-bounds accesses in RX fixup</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49051</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;net: usb: aqc111: Fix out-of-bounds accesses in RX fixup&lt;/p&gt;
&lt;p&gt;aqc111_rx_fixup() contains several out-of-bounds accesses that can be
triggered by a malicious (or defective) USB device, in particular:&lt;/p&gt;
&lt;p&gt;- The metadata array (desc_offset..desc_offset+2*pkt_count) can be out of bounds,
   causing OOB reads and (on big-endian systems) OOB endianness flips.
 - A packet can overlap the metadata array, causing a later OOB
   endianness flip to corrupt data used by a cloned SKB that has already
   been handed off into the network stack.
 - A packet SKB can be constructed whose tail is far beyond its end,
   causing out-of-bounds heap data to be considered part of the SKB&amp;#39;s
   data.&lt;/p&gt;
&lt;p&gt;Found doing variant analysis. Tested it with another driver (ax88179_178a), since
I don&amp;#39;t have a aqc111 device to test it, but the code looks very similar.&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;net: usb: aqc111: Fix out-of-bounds accesses in RX fixup&lt;/p&gt;
&lt;p&gt;aqc111_rx_fixup() contains several out-of-bounds accesses that can be
triggered by a malicious (or defective) USB device, in particular:&lt;/p&gt;
&lt;p&gt;- The metadata array (desc_offset..desc_offset+2*pkt_count) can be out of bounds,
   causing OOB reads and (on big-endian systems) OOB endianness flips.
 - A packet can overlap the metadata array, causing a later OOB
   endianness flip to corrupt data used by a cloned SKB that has already
   been handed off into the network stack.
 - A packet SKB can be constructed whose tail is far beyond its end,
   causing out-of-bounds heap data to be considered part of the SKB&amp;#39;s
   data.&lt;/p&gt;
&lt;p&gt;Found doing variant analysis. Tested it with another driver (ax88179_178a), since
I don&amp;#39;t have a aqc111 device to test it, but the code looks very similar.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49051</guid>
    </item>
  </channel>
</rss>
