<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:20:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99554 — net: usb: pegasus: do not advance rx_skb-&gt;data on dropped frames</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99554</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: pegasus: do not advance rx_skb-&amp;gt;data on dropped frames&lt;/p&gt;
&lt;p&gt;For the 0x8513 chip, read_bulk_callback() skips the 2-byte receive
header by advancing pegasus-&amp;gt;rx_skb-&amp;gt;data in place. This is done before
the pkt_len &amp;gt; PEGASUS_MTU check, and when that check drops the frame
the good path resubmits the same skb with the advanced rx_skb-&amp;gt;data as
the transfer buffer, still PEGASUS_MTU bytes long.&lt;/p&gt;
&lt;p&gt;Every frame with an oversized length field therefore moves the receive
buffer two more bytes towards the end of the skb data area. A device
that keeps sending such frames makes the host controller write received
data over skb_shared_info and past the end of the allocation, and the
corrupted skb_shared_info is used when the skb is eventually freed.
With an emulated device sending frames filled with 0x5a on a KASAN
kernel:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in dummy_timer+0xade/0x3f00 [dummy_hcd]
  Write of size 1536 at addr ffff888105821202 by task swapper/1/0
  ...
  Oops: general protection fault, probably for non-canonical address 0xeb4b474b4b4b4b4c: 0000 [#1] PREEMPT SMP KASAN NOPTI
  KASAN: maybe wild-memory-access in range [0x5a5a5a5a5a5a5a60-0x5a5a5a5a5a5a5a67]
  RIP: 0010:skb_release_data+0x36f/0x800&lt;/p&gt;
&lt;p&gt;Only skip the header with skb_reserve() once the frame is going to be
passed up, so the receive buffer always starts at the beginning of the
skb data area. Unlike the old pointer adjustment, skb_reserve() also
move…&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: pegasus: do not advance rx_skb-&amp;gt;data on dropped frames&lt;/p&gt;
&lt;p&gt;For the 0x8513 chip, read_bulk_callback() skips the 2-byte receive
header by advancing pegasus-&amp;gt;rx_skb-&amp;gt;data in place. This is done before
the pkt_len &amp;gt; PEGASUS_MTU check, and when that check drops the frame
the good path resubmits the same skb with the advanced rx_skb-&amp;gt;data as
the transfer buffer, still PEGASUS_MTU bytes long.&lt;/p&gt;
&lt;p&gt;Every frame with an oversized length field therefore moves the receive
buffer two more bytes towards the end of the skb data area. A device
that keeps sending such frames makes the host controller write received
data over skb_shared_info and past the end of the allocation, and the
corrupted skb_shared_info is used when the skb is eventually freed.
With an emulated device sending frames filled with 0x5a on a KASAN
kernel:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in dummy_timer+0xade/0x3f00 [dummy_hcd]
  Write of size 1536 at addr ffff888105821202 by task swapper/1/0
  ...
  Oops: general protection fault, probably for non-canonical address 0xeb4b474b4b4b4b4c: 0000 [#1] PREEMPT SMP KASAN NOPTI
  KASAN: maybe wild-memory-access in range [0x5a5a5a5a5a5a5a60-0x5a5a5a5a5a5a5a67]
  RIP: 0010:skb_release_data+0x36f/0x800&lt;/p&gt;
&lt;p&gt;Only skip the header with skb_reserve() once the frame is going to be
passed up, so the receive buffer always starts at the beginning of the
skb data area. Unlike the old pointer adjustment, skb_reserve() also
move…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99554</guid>
    </item>
  </channel>
</rss>
