CVE-2026-80824 — usb: usbfs: fix use-after-free of usb_device in usbdev_release()
In the Linux kernel, the following vulnerability has been resolved: usb: usbfs: fix use-after-free of usb_device in usbdev_release() usbdev_release() drops its reference to the struct usb_device before draining the list of completed async URBs, but that drain path reads back through the same object: free_async() calls dec_usb_memory_use_count() for any URB whose buffer came from the usbfs mmap() region, and its first statement is bus_to_hcd(ps->dev->bus). After a disconnect the usbfs reference can be the last one, in which case usb_put_dev() frees the device and the subsequent loop reads offset 80 of freed memory and uses the result as a struct usb_hcd *, which hcd_buffer_free_pages() then dereferences. This is reachable by an unprivileged process that has read/write access to a /dev/bus/usb node: mmap() the fd, submit one URB with a buffer inside the mapping, wait for the device to be unplugged, then munmap() and close(). It reproduces on every attempt rather than being a race, because a live MAP_SHARED vma holds a reference on the struct file, so usbdev_release() cannot run until the last vma is gone and the freeing branch of dec_usb_memory_use_count() is always taken. BUG: KASAN: slab-use-after-free in dec_usb_memory_use_count+0x3ae/0x410 Read of size 8 at addr ffff8880122ee050 by task poc/769 CPU: 1 UID: 1000 PID: 769 Comm: poc Tainted: G B 6.12.94 #3 Call Trace: dec_usb_memory_use_count+0x3ae/0x410 free_async+0x2aa/0x4f0 usbdev_release+0x375/0x460 __fput+0x3ea/0xb50 __x64_sys_close+0x86/0x100 Allocated by task 11: usb_alloc_dev+0x55/0xd90 hub_event+0x2524/0x43d0 Freed by task 769: kfree+0x121/0x360 device_release+0xd2/0x280 usb_put_dev+0x23/0x30 usbdev_release+0x2d8/0x460 Release the device reference after the drain loop instead. Nothing between the two points requires it to have been dropped.
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)+1
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 |
≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < 0a960b88c5979f853019d4dc4957dfbeeb193440≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < 96f5520fc9a5e4bbf77ac93c9d5ce502f597e6cf≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < bd4bffc621a8cb2f4d9ed9b6447415de524a3bef≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < 65879e0a452ca2a234b9475e0c11aff7a4343738≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < b3cde26a66b04f1d90ed0b675899c88b4e49d424≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < 5f08c45bdcfd28d1171de38c5ef29fc89a76eedc≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < 7f0278e474c4d1c4457974ff1137cc385c944ab3≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < 47a7f98fbb5006d46d15a3a210ffdc61448a4f19 and 2 more≥ f7d34b445abc00e979b7cf36b9580ac3d1a47cd8 and < 0dd68b5d01d022fc9c5e71c82a82b0a94d3d0671version 4.6 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.20%
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 · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/96f5520fc9a5e4bbf77ac93c9d5ce502f597e6cf
- git.kernel.org/stable/c/65879e0a452ca2a234b9475e0c11aff7a4343738
- git.kernel.org/stable/c/0dd68b5d01d022fc9c5e71c82a82b0a94d3d0671
- git.kernel.org/stable/c/47a7f98fbb5006d46d15a3a210ffdc61448a4f19
- git.kernel.org/stable/c/b3cde26a66b04f1d90ed0b675899c88b4e49d424
- git.kernel.org/stable/c/0a960b88c5979f853019d4dc4957dfbeeb193440
- github.com/advisories/GHSA-j9hx-p692-x42g
- git.kernel.org/stable/c/bd4bffc621a8cb2f4d9ed9b6447415de524a3bef
- git.kernel.org/stable/c/5f08c45bdcfd28d1171de38c5ef29fc89a76eedc
- git.kernel.org/stable/c/7f0278e474c4d1c4457974ff1137cc385c944ab3
- nvd.nist.gov/vuln/detail/CVE-2026-80824
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 7h
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 7h
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 7h
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 7h
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 7h
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 7h
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-80824 is "usb: usbfs: fix use-after-free of usb_device in usbdev_release()", 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.20% 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.