CVE-2026-23188 json
net: usb: r8152: fix resume reset deadlock
published 2026-02-14 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-5853
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
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 schedule_preempt_disabled+0x15/0x30 __mutex_lock_common+0x1fd/0x470 __rtl8152_set_mac_address+0x80/0x1f0 dev_set_mac_address+0x7f/0x150 rtl8152_post_reset+0x72/0x150 usb_reset_device+0x1d0/0x220 rtl8152_resume+0x99/0xc0 usb_resume_interface+0x3e/0xc0 usb_resume_both+0x104/0x150 usb_resume+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.
Patch / fix
- Linux Linux 6.12.70, 6.18.10, 6.19
- linux Debian 13 6.12.73-1
- linux Debian 14 6.18.10-1
debian advisories DEBIAN-CVE-2026-23188
- kernel-syms SLES 16.0, Linux Micro Extras 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
- kernel-obs-build Linux Micro Extras 6.2 6.12.0-160000.27.1
- kernel-rt Linux Micro 6.2 6.12.0-160000.27.1
- kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
- kernel-source SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
- kernel-default SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1
- kernel-default-base SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.27.1.160000.2.8
- kernel-azure SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.27.1
suse advisories SUSE-SU-2026:20873-1SUSE-SU-2026:20838-1SUSE-SU-2026:20931-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.27.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.27.1
opensuse advisories openSUSE-SU-2026:20416-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-23188 updated cvss 4.7
kernel: Linux kernel: Denial of Service in r8152 USB network adapter driver
-
Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
Sources
- CVE List CVE-2026-23188
- NVD CVE-2026-23188
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.