PT-2026-151765
CVE-2026-99554
·
Publicado
2026-11-19
·
Atualizado
2026-11-19
Descrição por
Pontuação
N/A
Não disponívelNão há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.
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).
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾