CVE-2026-23188
- Source
- https://cve.org/CVERecord?id=CVE-2026-23188
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-23188.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-23188
- Downstream
- Related
- Published
- 2026-02-14T16:27:16.869Z
- Modified
- 2026-04-02T17:30:12.643671171Z
- Summary
- net: usb: r8152: fix resume reset deadlock
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
net: usb: r8152: fix resume reset deadlock
rtl8152 can trigger device reset during reset which potentially can result in a deadlock:
**** DPM device timeout after 10 seconds; 15 seconds until panic **** Call Trace: <TASK> schedule+0x483/0x1370 schedulepreemptdisabled+0x15/0x30 __mutexlockcommon+0x1fd/0x470 __rtl8152setmacaddress+0x80/0x1f0 devsetmacaddress+0x7f/0x150 rtl8152postreset+0x72/0x150 usbresetdevice+0x1d0/0x220 rtl8152resume+0x99/0xc0 usbresumeinterface+0x3e/0xc0 usbresumeboth+0x104/0x150 usbresume+0x22/0x110
The problem is that rtl8152 resume calls reset under tp->control mutex while reset basically re-enters rtl8152 and attempts to acquire the same tp->control lock once again.
Reset INACCESSIBLE device outside of tp->control mutex scope to avoid recursive mutex_lock() deadlock.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23188.json" }- References
-
- https://git.kernel.org/stable/c/1b2efc593dca99d8e8e6f6d6c7ccd9a972679702
- https://git.kernel.org/stable/c/61c8091b7937f91f9bc0b7f6b578de270fe35dc7
- https://git.kernel.org/stable/c/6d06bc83a5ae8777a5f7a81c32dd75b8d9b2fe04
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23188.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-23188
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git