CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 230b1bc1310edcd5c1b71dcd6b77ccba43139cb5, 26838f147aeaa8f820ff799d72815fba5e209bd9, 9d86bc8b188a77c8d6f7252280ec2bd24ad6fbc1; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1.
Low priority for now. Upgrade to Linux Linux 230b1bc1310edcd5c1b71dcd6b77ccba43139cb5, 26838f147aeaa8f820ff799d72815fba5e209bd9, 9d86bc8b188a77c8d6f7252280ec2bd24ad6fbc1; azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 6.6.119.3-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: usb: renesas_usbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usb_f_ecm modprobe libcomposite modprobe configfs cd /sys/kernel/config/usb_gadget mkdir -p g1 cd g1 echo "0x1d6b" > idVendor echo "0x0104" > idProduct mkdir -p strings/0x409 echo "0123456789" > strings/0x409/serialnumber echo "Renesas." > strings/0x409/manufacturer echo "Ethernet Gadget" > strings/0x409/product mkdir -p functions/ecm.usb0 mkdir -p configs/c.1 mkdir -p configs/c.1/strings/0x409 echo "ECM" > configs/c.1/strings/0x409/configuration if [ ! -L configs/c.1/ecm.usb0 ]; then ln -s functions/ecm.usb0 configs/c.1 fi echo 11e20000.usb > UDC echo 11e20000.usb > /sys/bus/platform/drivers/renesas_usbhs/unbind The displayed trace is as follows: Internal error: synchronous external abort: 0000000096000010 [#1] SMP CPU: 0 UID: 0 PID: 188 Comm: sh Tainted: G M 6.17.0-rc7-next-20250922-00010-g41050493b2bd #55 PREEMPT Tainted: [M]=MACHINE_CHECK Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : usbhs_sys_function_pullup+0x10/0x40 [renesas_usbhs] lr : usbhsg_update_pullup+0x3c/0x68 [renesas_usbhs] sp : ffff8000838b3920 x29: ffff8000838b3920 x28: ffff00000d585780 x27: 0000000000000000 x26: 0000000000000000 x25: 0000000000000000 x24: ffff00000c3e3810 x23: ffff00000d5e5c80 x22: ffff00000d5e5d40 x21: 0000000000000000 x20: 0000000000000000 x19: ffff00000d5e5c80 x18: 0000000000000020 x17: 2e30303230316531 x16: 312d7968703a7968 x15: 3d454d414e5f4344 x14: 000000000000002c x13: 0000000000000000 x12: 0000000000000000 x11: ffff00000f358f38 x10: ffff00000f358db0 x9 : ffff00000b41f418 x8 : 0101010101010101 x7 : 7f7f7f7f7f7f7f7f x6 : fefefeff6364626d x5 : 8080808000000000 x4 : 000000004b5ccb9d x3 : 0000000000000000 x2 : 0000000000000000 x1 : ffff800083790000 x0 : ffff00000d5e5c80 Call trace: usbhs_sys_function_pullup+0x10/0x40 [renesas_usbhs] (P) usbhsg_pullup+0x4c/0x7c [renesas_usbhs] usb_gadget_disconnect_locked+0x48/0xd4 gadget_unbind_driver+0x44/0x114 device_remove+0x4c/0x80 device_release_driver_internal+0x1c8/0x224 device_release_driver+0x18/0x24 bus_remove_device+0xcc/0x10c device_del+0x14c/0x404 usb_del_gadget+0x88/0xc0 usb_del_gadget_udc+0x18/0x30 usbhs_mod_gadget_remove+0x24/0x44 [renesas_usbhs] usbhs_mod_remove+0x20/0x30 [renesas_usbhs] usbhs_remove+0x98/0xdc [renesas_usbhs] platform_remove+0x20/0x30 device_remove+0x4c/0x80 device_release_driver_internal+0x1c8/0x224 device_driver_detach+0x18/0x24 unbind_store+0xb4/0xb8 drv_attr_store+0x24/0x38 sysfs_kf_write+0x7c/0x94 kernfs_fop_write_iter+0x128/0x1b8 vfs_write+0x2ac/0x350 ksys_write+0x68/0xfc __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x34/0xf0 el0t_64_sync_handler+0xa0/0xe4 el0t_64_sync+0x198/0x19c Code: 7100003f 1a9f07e1 531c6c22 f9400001 (79400021) ---[ end trace 0000000000000000 ]--- note: sh[188] exited with irqs disabled note: sh[188] exited with preempt_count 1 The issue occurs because usbhs_sys_function_pullup(), which accesses the IP registers, is executed after the USBHS clocks have been disabled. The problem is reproducible on the Renesas RZ/G3S SoC starting with the addition of module stop in the clock enable/disable APIs. With module stop functionality enabled, a bus error is expected if a master accesses a module whose clock has been stopped and module stop activated. Disable the IP clocks at the end of remove.
- Published
- Dec 22, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
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
- 3.0affected
- f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and later · before fd1a7bf3a8cac13f6d2d52d8c7570ba41621db9aaffected · git
- f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and later · before cd5e86e34c66a831b5cb9b720ad411a006962cc8affected · git
- f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and later · before 230b1bc1310edcd5c1b71dcd6b77ccba43139cb5affected · git
- f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and later · before 9d86bc8b188a77c8d6f7252280ec2bd24ad6fbc1affected · git
- f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and later · before 26838f147aeaa8f820ff799d72815fba5e209bd9affected · git
- f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and later · before aa658a6d5ac21c7cde54c6d015f2d4daff32e02daffected · git
- f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and later · before eb9ac779830b2235847b72cb15cf07c7e3333c5eaffected · git
- before 3.0not affected · semver
- 5.10.247 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 | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.11-1 | 6.17.11-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
Published before and after this one in the same product
- ← EarlierCVE-2025-68325Dec 18, 2025 · net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop0Monitor
- ← EarlierCVE-2025-68326Dec 22, 2025 · drm/xe/guc: Fix stack_depot usage0Monitor
- Later →CVE-2025-68328Dec 22, 2025 · firmware: stratix10-svc: fix bug in saving controller data0Monitor
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 | 230b1bc1310edcd5c1b71dcd6b77ccba43139cb5 | Vendor (CNA) |
| Linux Linux | 26838f147aeaa8f820ff799d72815fba5e209bd9 | Vendor (CNA) |
| Linux Linux | 9d86bc8b188a77c8d6f7252280ec2bd24ad6fbc1 | Vendor (CNA) |
| Linux Linux | aa658a6d5ac21c7cde54c6d015f2d4daff32e02d | Vendor (CNA) |
| Linux Linux | cd5e86e34c66a831b5cb9b720ad411a006962cc8 | Vendor (CNA) |
| Linux Linux | eb9ac779830b2235847b72cb15cf07c7e3333c5e | Vendor (CNA) |
| Linux Linux | fd1a7bf3a8cac13f6d2d52d8c7570ba41621db9a | Vendor (CNA) |
| azl3 kernel 6.6.117.1-1 on Azure Linux 3.0 | 6.6.119.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.159-1 · 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.
No history yet (it accumulates with the daily EPSS job).
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
Show all references (6 more)Show less
- git.kernel.org/stable/c/26838f147aeaa8f820ff799d72815fba5e209bd9
- git.kernel.org/stable/c/9d86bc8b188a77c8d6f7252280ec2bd24ad6fbc1
- git.kernel.org/stable/c/aa658a6d5ac21c7cde54c6d015f2d4daff32e02d
- git.kernel.org/stable/c/cd5e86e34c66a831b5cb9b720ad411a006962cc8
- git.kernel.org/stable/c/eb9ac779830b2235847b72cb15cf07c7e3333c5e
- git.kernel.org/stable/c/fd1a7bf3a8cac13f6d2d52d8c7570ba41621db9a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.