usb: gadget: goku_udc: avoid NULL deref of dev->driver in INT_USBRESET log
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.
- Published
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.2% · 6th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d7b33afbf9b54b61cb423af9663df54eae11d3b1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ea2901a4a90afc662e4d023542d91f10ab10fd3caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 999ff3bf665f2abfb6af519ef3d6d42b061d3c15affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a018d4195114ca2cf79858cc45c98581dee4795baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 10d7fc3008d5b7ec03af8e08927f1d090014c2afaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 28d78783a871cdb7a637dcb72452ff7d303430aeaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5bf5e3fba9bc7dfd69701521dbe9809f8ccbdb02affected · git
- before 2.6.12not affected · semver
- 5.10.271 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 10d7fc3008d5b7ec03af8e08927f1d090014c2af | Vendor (CNA) |
| Linux Linux | 28d78783a871cdb7a637dcb72452ff7d303430ae | Vendor (CNA) |
| Linux Linux | 5bf5e3fba9bc7dfd69701521dbe9809f8ccbdb02 | Vendor (CNA) |
| Linux Linux | 999ff3bf665f2abfb6af519ef3d6d42b061d3c15 | Vendor (CNA) |
| Linux Linux | a018d4195114ca2cf79858cc45c98581dee4795b | Vendor (CNA) |
| Linux Linux | d7b33afbf9b54b61cb423af9663df54eae11d3b1 | Vendor (CNA) |
| Linux Linux | ea2901a4a90afc662e4d023542d91f10ab10fd3c | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/10d7fc3008d5b7ec03af8e08927f1d090014c2af
- git.kernel.org/stable/c/28d78783a871cdb7a637dcb72452ff7d303430ae
- git.kernel.org/stable/c/5bf5e3fba9bc7dfd69701521dbe9809f8ccbdb02
- git.kernel.org/stable/c/999ff3bf665f2abfb6af519ef3d6d42b061d3c15
- git.kernel.org/stable/c/a018d4195114ca2cf79858cc45c98581dee4795b
- git.kernel.org/stable/c/d7b33afbf9b54b61cb423af9663df54eae11d3b1
- git.kernel.org/stable/c/ea2901a4a90afc662e4d023542d91f10ab10fd3c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.