In the Linux kernel, the following vulnerability has been resolved:
USB: core: Limit the length of unkillable synchronous timeouts
The usb_control_msg(), usb_bulk_msg(), and usb_interrupt_msg() APIs in
usbcore allow unlimited timeout durations. And since they use
uninterruptible waits, this leaves open the possibility of hanging a
task for an indefinitely long time, with no way to kill it short of
unplugging the target device.
To prevent this sort of problem, enforce a maximum limit on the length
of these unkillable timeouts. The limit chosen here, somewhat
arbitrarily, is 60 seconds. On many systems (although not all) this
is short enough to avoid triggering the kernel's hung-task detector.
In addition, clear up the ambiguity of negative timeout values by
treating them the same as 0, i.e., using the maximum allowed timeout.
CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 4e86f5b79e62ded7e3c3ebd688cf5775e618148a; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 06d2bbc4c66c6b0e8a43728c4949026026a5be67; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 6c62935670acdbb7687ced20494923b66fbb0367; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 659c0c7d50a4b0f6aa197c4c098cfd91daf63862; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 24b31a227f679a942d820840a4dea7f0c09a387f; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 64f3d75633aedc12bdff220e9a4337177430bd9d; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 2d34cb4d1d6283b4be9c78f4a83ed6956d3069ec; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 1015c27a5e1a63efae2b18a9901494474b4d1dc3
from 2.6.12.1 before 5.10.253; from 5.11 before 5.15.203; from 5.16 before 6.1.167; from 6.2 before 6.6.130; from 6.7 before 6.12.78; from 6.13 before 6.18.19; from 6.19 before 6.19.9; 2.6.12; and 8 more ranges
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.