CVE-2026-63905 — usbip: vudc: Fix use after free bug in vudc_remove due to race condition
In the Linux kernel, the following vulnerability has been resolved: usbip: vudc: Fix use after free bug in vudc_remove due to race condition This patch follows up Zheng Wang's 2023 report of a use-after-free in vudc_remove(). The original thread stalled on Shuah Khan's request for runtime testing of the unplug/unbind path. This patch supplies that testing and keeps Zheng's original fix shape. In vudc_probe(), v_init_timer() binds udc->tr_timer.timer to v_timer(). usbip_sockfd_store() starts the timer via v_start_timer()/v_kick_timer(). vudc_remove() can then free the containing struct vudc while the timer is still pending or executing. KASAN confirms the race on an unpatched x86_64 QEMU guest with CONFIG_KASAN=y, CONFIG_USBIP_VUDC=y, CONFIG_USB_ZERO=y, and a tight loop that repeatedly writes a socket fd to usbip_sockfd, closes the socket pair, and unbinds/rebinds usbip-vudc.0: BUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x8ba/0x8e0 Write of size 8 at addr ffff888001b80740 by task trigger_and_unb/239 Allocated by task 239: vudc_probe+0x4d/0xaa0 Freed by task 239: kfree+0x18f/0x520 device_release_driver_internal+0x388/0x540 unbind_store+0xd9/0x100 This lands in the timer core rather than v_timer() itself because the embedded timer_list is being walked after its containing struct vudc has already been freed. The underlying lifetime bug is the same one Zheng reported. With v_stop_timer() called from vudc_remove() and the timer deleted synchronously, the same harness completed 5000 bind/unbind iterations with no KASAN report.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < 61704e5cf9cd7464b510eb606e7e2978b1160a64≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < dcc1c90b28b28b7c493547506297e78653f81952≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < 1036ac6148995feaf486014d32bf26bf993c06a9≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < a0638db2340ee053ab0450656a763fd111475e54≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < d07ed707467ce05ea9c03412d0c5ee9d0fe386a6≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < 88d459e5b5a46da1ef9fd6f52d9439343edeec88≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < 207bf80362df3fce8ebc9723351dcb1bc6d9ed0f≥ b6a0ca11186759ad7045d68a5447b1e89f658384 and < d96209626a29ea64666be98c30b30ac82e5f1be6 and 1 moreversion 4.7 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/d07ed707467ce05ea9c03412d0c5ee9d0fe386a6
- git.kernel.org/stable/c/207bf80362df3fce8ebc9723351dcb1bc6d9ed0f
- git.kernel.org/stable/c/88d459e5b5a46da1ef9fd6f52d9439343edeec88
- git.kernel.org/stable/c/a0638db2340ee053ab0450656a763fd111475e54
- git.kernel.org/stable/c/61704e5cf9cd7464b510eb606e7e2978b1160a64
- git.kernel.org/stable/c/d96209626a29ea64666be98c30b30ac82e5f1be6
- git.kernel.org/stable/c/1036ac6148995feaf486014d32bf26bf993c06a9
- git.kernel.org/stable/c/dcc1c90b28b28b7c493547506297e78653f81952
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 15h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 15h
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-63905 is "usbip: vudc: Fix use after free bug in vudc_remove due to race condition", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.