Heap out-of-bounds write in Linux kernel usbip_pack_ret_submit()
CVE-2026-31607 is a Linux kernel USB/IP client-side memory corruption vulnerability in the handling of RET_SUBMIT responses for isochronous URBs. In usbip_pack_ret_submit(), the client unconditionally overwrites urb->number_of_packets with the number_of_packets value received from the network PDU. That field is later used as the loop bound in usbip_recv_iso() and usbip_pad_iso() to iterate over urb->iso_frame_desc[], a flexible array whose size was fixed when the URB was originally allocated based on the number_of_packets from the earlier CMD_SUBMIT request. A malicious USB/IP server can return a RET_SUBMIT response with number_of_packets larger than the original submitted value, causing usbip_recv_iso() to write past the end of urb->iso_frame_desc[] and trigger a heap out-of-bounds write. The issue was confirmed by KASAN on kernel 7.0.0-rc5 as a slab-out-of-bounds write in usbip_recv_iso(). The fix adds validation in usbip_pack_ret_submit() to ensure rpdu->number_of_packets does not exceed the original urb->number_of_packets before overwriting it; invalid values are clamped to zero so downstream receive/padding paths return safely.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.