usb: gadget: ncm: Fix handling of zero block length packets
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e2dbfea520e60d58e0c498ba41bde10452257779, Kernel f90ce1e04cbcc76639d6cba0fdbd820cd80b3c70, Kernel 7664ee8bd80309b90d53488b619764f0a057f2b7 and 14 more.
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: ncm: Fix handling of zero block length packets While connecting to a Linux host with CDC_NCM_NTB_DEF_SIZE_TX set to 65536, it has been observed that we receive short packets, which come at interval of 5-10 seconds sometimes and have block length zero but still contain 1-2 valid datagrams present. According to the NCM spec: "If wBlockLength = 0x0000, the block is terminated by a short packet. In this case, the USB transfer must still be shorter than dwNtbInMaxSize or dwNtbOutMaxSize. If exactly dwNtbInMaxSize or dwNtbOutMaxSize bytes are sent, and the size is a multiple of wMaxPacketSize for the given pipe, then no ZLP shall be sent. wBlockLength= 0x0000 must be used with extreme care, because of the possibility that the host and device may get out of sync, and because of test issues. wBlockLength = 0x0000 allows the sender to reduce latency by starting to send a very large NTB, and then shortening it when the sender discovers that there’s not sufficient data to justify sending a large NTB" However, there is a potential issue with the current implementation, as it checks for the occurrence of multiple NTBs in a single giveback by verifying if the leftover bytes to be processed is zero or not. If the block length reads zero, we would process the same NTB infintely because the leftover bytes is never zero and it leads to a crash. Fix this by bailing out if block length reads zero.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=ff3ba016263ee93a1c6209bf5ab1599de7ab1512 <e2dbfea520e60d58e0c498ba41bde10452257779, >=427694cfaafa565a3db5c5ea71df6bc095dca92f <f90ce1e04cbcc76639d6cba0fdbd820cd80b3c70, >=49fbc18378ae72a47feabee97fdb86f3cea09765 <7664ee8bd80309b90d53488b619764f0a057f2b7, >=5.10.199 <5.10.215, >=5.15.136 <5.15.154, >=5.4.259 <5.4.274, >=6.1.59 <6.1.84, >=6.5.8 <6.6, >=7014807fb7efa169a47a7a0a0a41d2c513925de0 <92b051b87658df7649ffcdef522593f21a2b296b, >=e7ca00f35d8a17af1ae19d529193ebc21bfda164 <a766761d206e7c36d7526e0ae749949d17ca582c, =4bf1a9d20c65b9e80ca4b171267103f8d4f2c61f, =5bdf93a2f5459f944b416b188178ca4a92fd206f, =6.6, >=17c653d4913bbc50d284aa96cf12bfc63e41ee5c <ef846cdbd100f7f9dc045e8bcd7fe4b3a3713c03, >=4.14.328 <4.15, >=4.19.297 <4.19.312, >=427694cfaafa565a3db5c5ea71df6bc095dca92f <6b2c73111a252263807b7598682663dc33aa4b4c, >=427694cfaafa565a3db5c5ea71df6bc095dca92f <a0f77b5d6067285b8eca0ee3bd1e448a6258026f | e2dbfea520e60d58e0c498ba41bde10452257779, f90ce1e04cbcc76639d6cba0fdbd820cd80b3c70, 7664ee8bd80309b90d53488b619764f0a057f2b7, 5.10.215, 5.15.154, 5.4.274, 6.1.84, 6.6, 92b051b87658df7649ffcdef522593f21a2b296b, a766761d206e7c36d7526e0ae749949d17ca582c, ef846cdbd100f7f9dc045e8bcd7fe4b3a3713c03, 4.15, 4.19.312, 6b2c73111a252263807b7598682663dc33aa4b4c, a0f77b5d6067285b8eca0ee3bd1e448a6258026f |
| linux-kernel: Kernel | >=4.19.297 <4.19.312, >=5.10.199 <5.10.215, >=5.15.136 <5.15.154, >=5.4.259 <5.4.274, >=6.1.59 <6.1.84, >=6.5.8 <6.6, >=6.6.0 <6.6.24, >=6.7.0 <6.7.12, >=4.14.328 <4.15 | 4.19.312, 5.10.215, 5.15.154, 5.4.274, 6.1.84, 6.6, 6.6.24, 6.7.12, 4.15 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket