cbcvebase.
CVE-2024-35825
published 2024-05-17

CVE-2024-35825: 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…

PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
13.9th percentile
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

37 ranges· showing 25
VendorProductVersion rangeFixed in
debiandebian_linux
debianlinux< linux 6.1.85-1 (bookworm)linux 6.1.85-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux
linuxlinux>= 17c653d4913bbc50d284aa96cf12bfc63e41ee5c < ef846cdbd100f7f9dc045e8bcd7fe4b3a3713c03ef846cdbd100f7f9dc045e8bcd7fe4b3a3713c03
linuxlinux>= 4.14.328 < 4.154.15
linuxlinux>= 4.19.297 < 4.19.3124.19.312
linuxlinux>= 427694cfaafa565a3db5c5ea71df6bc095dca92f < a0f77b5d6067285b8eca0ee3bd1e448a6258026fa0f77b5d6067285b8eca0ee3bd1e448a6258026f
linuxlinux>= 427694cfaafa565a3db5c5ea71df6bc095dca92f < 6b2c73111a252263807b7598682663dc33aa4b4c6b2c73111a252263807b7598682663dc33aa4b4c
linuxlinux>= 427694cfaafa565a3db5c5ea71df6bc095dca92f < f90ce1e04cbcc76639d6cba0fdbd820cd80b3c70f90ce1e04cbcc76639d6cba0fdbd820cd80b3c70
linuxlinux>= 49fbc18378ae72a47feabee97fdb86f3cea09765 < 7664ee8bd80309b90d53488b619764f0a057f2b77664ee8bd80309b90d53488b619764f0a057f2b7
linuxlinux>= 5.10.199 < 5.10.2155.10.215
linuxlinux>= 5.15.136 < 5.15.1545.15.154
linuxlinux>= 5.4.259 < 5.4.2745.4.274
linuxlinux>= 6.1.59 < 6.1.846.1.84
linuxlinux>= 6.5.8 < 6.66.6
linuxlinux>= 7014807fb7efa169a47a7a0a0a41d2c513925de0 < 92b051b87658df7649ffcdef522593f21a2b296b92b051b87658df7649ffcdef522593f21a2b296b
linuxlinux>= e7ca00f35d8a17af1ae19d529193ebc21bfda164 < a766761d206e7c36d7526e0ae749949d17ca582ca766761d206e7c36d7526e0ae749949d17ca582c
linuxlinux>= ff3ba016263ee93a1c6209bf5ab1599de7ab1512 < e2dbfea520e60d58e0c498ba41bde10452257779e2dbfea520e60d58e0c498ba41bde10452257779
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.216-15.10.216-1
linuxlinux_kernel>= 0 < 6.1.85-16.1.85-1
linuxlinux_kernel>= 0 < 6.7.12-16.7.12-1

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.0HIGH
vendor_ubuntu7.0HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.