usbip: vudc: fix NULL deref in vep_dequeue()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.261, Kernel 5.15.212, Kernel 6.1.178 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: usbip: vudc: fix NULL deref in vep_dequeue() vep_alloc_request() wasn't initializing vrequest->udc, so cancellations on the FunctionFS AIO path were arriving in vep_dequeue without a valid UDC reference. Since vrequest->udc is never actually properly used anywhere, we opt to remove it, and update vep_dequeue to obtain a reference to the udc with ep_to_vudc(), consistent with the other vep_ ops. AFAICT this bug has existed for ~10 years. Seems that nobody has really stressed the FunctionFS AIO path on usbip's vudc. I tested this fix in a QEMU aarch64 guest driving FunctionFS endpoints via AIO. Before the fix, running `usbip attach` from the host would cause the guest to oops with the following backtrace: Call trace: vep_dequeue+0x1c/0xe4 (P) usb_ep_dequeue+0x14/0x20 ffs_aio_cancel+0x24/0x34 __arm64_sys_io_cancel+0xb0/0x124 do_el0_svc+0x68/0x100 el0_svc+0x18/0x5c el0t_64_sync_handler+0x98/0xdc el0t_64_sync+0x154/0x158
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=4.7 <5.10.261, >=5.11 <5.15.212, >=5.16 <6.1.178, >=6.13 <6.18.39, >=6.19 <7.1.4, >=6.2 <6.6.145, >=6.7 <6.12.96, =7.2, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <0443e4416aa1ee97748d1ed904eaf3352c60045e, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <1226293ec9bed3d4cc5b05eeeb811d315ca51652, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <347b59e9f96719d89b6ef555d02a18ada1a5846f, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <3750f75f29f99c0223601e2ee73ad084adec47bd, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <9858c91d9ee6a13c45311569039413729fc9b757, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <c5371e0b91b24159a3ebaa61e70b0980bcf03c0a, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <d0ebf9cc7c2ddf95a7cfc654b940bdacb7edde97, =4.7, >=b6a0ca11186759ad7045d68a5447b1e89f658384 <0025276175fbbe0dcbf3f84d090b0adee769e9d9 | 5.10.261, 5.15.212, 6.1.178, 6.18.39, 7.1.4, 6.6.145, 6.12.96, 0443e4416aa1ee97748d1ed904eaf3352c60045e, 1226293ec9bed3d4cc5b05eeeb811d315ca51652, 347b59e9f96719d89b6ef555d02a18ada1a5846f, 3750f75f29f99c0223601e2ee73ad084adec47bd, 9858c91d9ee6a13c45311569039413729fc9b757, c5371e0b91b24159a3ebaa61e70b0980bcf03c0a, d0ebf9cc7c2ddf95a7cfc654b940bdacb7edde97, 0025276175fbbe0dcbf3f84d090b0adee769e9d9 |
| linux-kernel: Kernel | >=4.7.0 <5.10.261, >=5.11.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.39, >=6.19.0 <7.1.4, >=6.2.0 <6.6.145, >=6.7.0 <6.12.96 | 5.10.261, 5.15.212, 6.1.178, 6.18.39, 7.1.4, 6.6.145, 6.12.96 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket