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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can deadlock systems using the rtl8152 USB Ethernet driver during resume and device reset. The observed impact is availability: a resume path can stall long enough to trigger a device power-management timeout and possible panic. No source here reports active exploitation.
Executive priority
Treat as a targeted availability risk, not an emergency internet-facing compromise based on available evidence. Patch during normal kernel maintenance, with higher priority for laptops, appliances, or operational systems using USB Ethernet and power management.
Technical view
The rtl8152 resume path calls USB reset while holding tp->control. Reset re-enters rtl8152 through post-reset MAC address handling and attempts to acquire the same mutex, causing a recursive mutex deadlock. The fix moves reset of an inaccessible device outside the tp->control mutex scope.
Likely exposure
Exposure is most likely on Linux systems with Realtek rtl8152 USB Ethernet devices or the r8152 driver enabled, running affected kernel builds. The source lists Linux kernel affected entries but lacks clear distro package mapping.
Exploitation context
The provided sources describe a deadlock during resume/reset, not a remote code execution path. KEV is false, and no cited source claims exploitation in the wild. Practical impact appears to be local availability loss under device resume conditions.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. Severity, CVSS, CWE, exploitability, and exact distro impact are not provided. The vulnerable pattern is a mutex re-entry deadlock in the r8152 resume/reset flow.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Check Linux distribution advisories for backported r8152 fixes.
Prioritize systems dependent on USB Ethernet during suspend/resume workflows.
If no update exists, follow vendor guidance for temporary operational workarounds.
Validation and detection
Inventory kernels running the r8152 or rtl8152 USB Ethernet driver.
Confirm whether vendor kernels include the referenced stable commits.
Review suspend/resume logs for DPM timeout or rtl8152 reset deadlock symptoms.
Track CVE and distribution advisories for affected package mapping.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23188 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 16:27 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.