CVE-2026-99554: net: usb: pegasus: do not advance rx_skb->data on dropped frames

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

net: usb: pegasus: do not advance rxskb->data on dropped frames

For the 0x8513 chip, readbulkcallback() skips the 2-byte receive header by advancing pegasus->rxskb->data in place. This is done before the pktlen > PEGASUSMTU check, and when that check drops the frame the good path resubmits the same skb with the advanced rxskb->data as the transfer buffer, still PEGASUSMTU bytes long.

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 skbsharedinfo and past the end of the allocation, and the corrupted skbsharedinfo is used when the skb is eventually freed. With an emulated device sending frames filled with 0x5a on a KASAN kernel:

BUG: KASAN: slab-out-of-bounds in dummytimer+0xade/0x3f00 [dummyhcd] 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:skbreleasedata+0x36f/0x800

Only skip the header with skbreserve() 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, skbreserve() also moves skb->tail, so the two header bytes now count against the buffer size: lower the length limit for the 0x8513 accordingly, otherwise a pktlen of PEGASUSMTU - 1 or PEGASUSMTU would trip skboverpanic().

Found by code review with LLM assistance and reproduced with an emulated USB device (raw-gadget + dummyhcd).

Affected Software

7 affected componentsFixes available
linux/kernel>=2.6.12<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2
debian/linux*
debian/linux<6.12.117-1
6.12.117-1
debian/linux<7.3.3-1
7.3.3-1
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1
6.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1
  5. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.3-1
  6. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1
  7. Compensating control

    In the Pegasus USB receive path, do not advance rx_skb->data for frames that are dropped. Skip the 2-byte header with skb_reserve() only after the frame passes the length check and will be delivered; lower the 0x8513 pkt_len limit accordingly so the receive buffer remains within PEGASUS_MTU.

Event History

Nov 19, 2026
CVE Published
via MITRE·02:45 PM
Data Sourced
via MITRE·02:45 PM
Description
Data Sourced
via OSV·02:45 PM
DescriptionAffected Software
Data Sourced
via NVD·03:18 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203