CVE-2026-64331None▾ SunlitIn 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_de…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.1%
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
Linux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < 9858c91d9ee6a13c45311569039413729fc9b757Linux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < 1226293ec9bed3d4cc5b05eeeb811d315ca51652Linux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < 3750f75f29f99c0223601e2ee73ad084adec47bdLinux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < d0ebf9cc7c2ddf95a7cfc654b940bdacb7edde97Linux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < 0025276175fbbe0dcbf3f84d090b0adee769e9d9Linux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < 347b59e9f96719d89b6ef555d02a18ada1a5846fLinux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < 0443e4416aa1ee97748d1ed904eaf3352c60045eLinux >= b6a0ca11186759ad7045d68a5447b1e89f658384 < c5371e0b91b24159a3ebaa61e70b0980bcf03c0aLinux 4.7Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses