CVE-2026-97482

usb: gadget: goku_udc: avoid NULL deref of dev->driver in INT_USBRESET log

N/A
Published: September 24, 2026 at 04:04 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: goku_udc: avoid NULL deref of dev->driver in INT_USBRESET log goku_irq() handles a number of bus events under a single ep0 path. It already guards the gadget driver suspend/resume callbacks against a NULL ->driver: if (dev->gadget.speed != USB_SPEED_UNKNOWN && dev->driver && dev->driver->resume) { spin_unlock(&dev->lock); dev->driver->resume(&dev->gadget); ... } but the very next branch unconditionally dereferences dev->driver when an INT_USBRESET arrives: if (stat & INT_USBRESET) { ACK(INT_USBRESET); INFO(dev, "USB reset done, gadget %s\n", dev->driver->driver.name); } If the controller raises INT_USBRESET before any gadget driver has been bound (or after one has been unbound), dev->driver is NULL and the printk dereferences NULL. smatch flags the inconsistency: drivers/usb/gadget/udc/goku_udc.c:1618 goku_irq() error: we previously assumed 'dev->driver' could be null (see line 1607) Fall back to a placeholder when the gadget driver is not bound. No functional change while a gadget driver is bound.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2712.6.12 ≤ v < 5.15.2222.6.12 ≤ v < 6.1.1892.6.12 ≤ v < 6.12.1112.6.12 ≤ v < 6.18.532.6.12 ≤ v < 6.6.1582.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 10d7fc3008d5b7ec03af8e08927f1d090014c2af (fixed)
Vendor states this is fixed in 28d78783a871cdb7a637dcb72452ff7d303430ae (fixed)
Vendor states this is fixed in 5bf5e3fba9bc7dfd69701521dbe9809f8ccbdb02 (fixed)
Vendor states this is fixed in 999ff3bf665f2abfb6af519ef3d6d42b061d3c15 (fixed)
Vendor states this is fixed in a018d4195114ca2cf79858cc45c98581dee4795b (fixed)
Vendor states this is fixed in d7b33afbf9b54b61cb423af9663df54eae11d3b1 (fixed)
Vendor states this is fixed in ea2901a4a90afc662e4d023542d91f10ab10fd3c (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card