From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795100794; b=cl0D1K0qt+Q1bVudTawk4Z4S9p0Hw3VTLQ3bn/NTpa81jht2pLyUHmulceA3kyT0DRww y25fPGvGnPVUt4OIOTeirlMDpn74NMQ4n3CcW42UeELTILT3B6OuN7/lAgaPgB8BwlWei bQMmTRZ7OxvW2XWlOfm8xdDob9XAmsWlkeItDYDcHGWKii736K6CrzBkJpq2f42fzT+0L dUTq0Z318TwnClayf7DcbMB7GIRPxVPmY0c964+qasU7aqJQxkpv1sSHcF4eEL0FwetVn Qv+Ukd3yLbkPR5PWlNXxlcL4jmyrLH6zaT56ZAJc6WxgBnP1CJsJ8zElhwCxdcqpgKQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795100794; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=sXUieiOpPGlpEMq+boojRdVSZknRRX4LwbCiyatJSHQ=; b=cD4lAszl3qrN7SIJcD6U45hBXZ+Rh6sz/gjFVsQAdbfmxLbjOhSxPy93bWKXejJ/eq99 HRwL14wIgLI55h5SExBxBcT6LyIJsWphrbPhqpVdkqmOUDRM/AiMf9DOgtV6oRAVOEXX+ TZJIYFfdSOtMYmMtCc55hwDzjKml7P3b+Y4FC5k7iGaOJQQmLK5W4/1F11EhtMOcLJgOs D704sR/87Jwj3uj3YD3xmDq2mRyJ4KZsURuCY5042eZ7g0Nav1LZQLNde0FXrdhvBNWYf e09DhCVRTE98pvbhHf/tAd+c6SC3cXdNXHs0q7ns7o45yjXyElfpjMdrRYwPBqHO+SQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=aUNrX0QO; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 99676607169A for ; Thu, 19 Nov 2026 15:06:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=aUNrX0QO Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3905C1F00926; Thu, 19 Nov 2026 15:06:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795100794; bh=sXUieiOpPGlpEMq+boojRdVSZknRRX4LwbCiyatJSHQ=; h=From:To:Cc:Subject:Date:Reply-To; b=aUNrX0QOU8Gt0ON7/5NqsyXDKh0EFvoUaS3kQ6o18OCq37BguQ1XK+vFS4iNXUxFo mvw1GHRACwSCTiCVdD8uxMmd0tegbaAIdiJdlGPfH7SxOPOMwPyDMtBsP83HJfMgKA w5/sB9IED5oF67JcwHqk4fCVFFyZvDZ62BlOrgtQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99554: net: usb: pegasus: do not advance rx_skb->data on dropped frames Date: Thu, 19 Nov 2026 15:27:32 +0100 Message-ID: <2026111927-CVE-2026-99554-bc7a@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3951; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Hs6tb4z6ntvKkP245ceomYOo1sM7hXEibNGImJSxMzQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2WbP2GIm6mopvypj8z7X34xL2VdP8A9Kmh2v5XJNy YK57PqajlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjIW32G+aHlhq/bI6t/39Mx YHMKOcE8MW1SEMM8o3fmf69mK1bnTLXlNH9R/zArfVMvAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: net: usb: pegasus: do not advance rx_skb->data on dropped frames For the 0x8513 chip, read_bulk_callback() skips the 2-byte receive header by advancing pegasus->rx_skb->data in place. This is done before the pkt_len > PEGASUS_MTU check, and when that check drops the frame the good path resubmits the same skb with the advanced rx_skb->data as the transfer buffer, still PEGASUS_MTU 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 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: 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 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 moves skb->tail, so the two header bytes now count against the buffer size: lower the length limit for the 0x8513 accordingly, otherwise a pkt_len of PEGASUS_MTU - 1 or PEGASUS_MTU would trip skb_over_panic(). Found by code review with LLM assistance and reproduced with an emulated USB device (raw-gadget + dummy_hcd). The Linux kernel CVE team has assigned CVE-2026-99554 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.117 with commit 05e204042f213f9d862c6901f53cece61aa5209c Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18.61 with commit 00c0c940c1c8941497a8cf511edc95fdde8c6382 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3.2 with commit 6af7578840bde82e6cd5de3235502c116bcc196c Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.4-rc1 with commit bfa09dccf98cf78dd9282259b2140bd1472f5ae9 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-99554 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/net/usb/pegasus.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/05e204042f213f9d862c6901f53cece61aa5209c https://git.kernel.org/stable/c/00c0c940c1c8941497a8cf511edc95fdde8c6382 https://git.kernel.org/stable/c/6af7578840bde82e6cd5de3235502c116bcc196c https://git.kernel.org/stable/c/bfa09dccf98cf78dd9282259b2140bd1472f5ae9