usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed
CVE-2026-89738 · published 11 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-89738?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 4037242c4f5ff77afe61bf07ca1e8a99490219e5 to < 723d73b245843d4fff4c3f42e857c78c2b2d414e, 4037242c4f5ff77afe61bf07ca1e8a99490219e5 to < a2a602cb1e28d76a5398cec3fa21b0110385f501, 4037242c4f5ff77afe61bf07ca1e8a99490219e5 to < 51a311eb97e91ce1aed3005cb71ccb2e30f8cce8, 4037242c4f5ff77afe61bf07ca1e8a99490219e5 to < 557ef547d49ff5e6026a4d39bdd3113bd81d7688
- Linux Linux: 2.6.36
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed
In polled-VBUS mode (board.vbus_pin && board.vbus_polled), probe arms a
self-restarting cycle: at91_vbus_timer() schedules vbus_timer_work, and
at91_vbus_timer_work() calls at91_vbus_update() and re-arms the timer via
mod_timer(). Both recover the same udc through container_of and dereference
it on every iteration.
Neither teardown path cancels this cycle. udc is devm-allocated, so it is
freed after at91udc_remove() returns, and is likewise freed when probe
fails and devres runs. A timer callback or work item that is pending or
running at either point dereferences the freed udc.
Add at91_udc_shutdown_vbus_timer() and call it from at91udc_remove() and
from the usb_add_gadget_udc() failure path in probe; the remaining probe
error paths fail before the timer is armed. timer_shutdown_sync() waits
for a running callback and clears timer->function, which makes the work
handler's mod_timer() a permanent no-op; cancel_work_sync() then drains
any pending or running work whose re-arm attempt now does nothing. The
timer must be shut down first, since cancelling the work alone would let
the timer re-queue it. The guard mirrors probe: in IRQ mode the timer and
work_struct are never initialized.
This does not require a fault; a normal driver unbind can interleave with
an already queued work item.
This issue was found by an in-house static analysis tool.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/723d73b245843d4fff4c3f42e857c78c2b2d414e
- git.kernel.org/stable/c/a2a602cb1e28d76a5398cec3fa21b0110385f501
- git.kernel.org/stable/c/51a311eb97e91ce1aed3005cb71ccb2e30f8cce8
- git.kernel.org/stable/c/557ef547d49ff5e6026a4d39bdd3113bd81d7688
- git.kernel.org/stable/c/c27d13ce4bab80fbdf6523928071b6c24b37606c
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON