VYPR
Medium severity5.5NVD Advisory· Published Apr 3, 2026· Updated Apr 23, 2026

CVE-2026-23446

CVE-2026-23446

Description

In the Linux kernel, the following vulnerability has been resolved:

net: usb: aqc111: Do not perform PM inside suspend callback

syzbot reports "task hung in rpm_resume"

This is caused by aqc111_suspend calling the PM variant of its write_cmd routine.

The simplified call trace looks like this:

rpm_suspend() usb_suspend_both() - here udev->dev.power.runtime_status == RPM_SUSPENDING aqc111_suspend() - called for the usb device interface aqc111_write32_cmd() usb_autopm_get_interface() pm_runtime_resume_and_get() rpm_resume() - here we call rpm_resume() on our parent rpm_resume() - Here we wait for a status change that will never happen.

At this point we block another task which holds rtnl_lock and locks up the whole networking stack.

Fix this by replacing the write_cmd calls with their _nopm variants

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

In the Linux kernel's aqc111 driver, calling PM-aware write functions during suspend causes a deadlock that hangs the networking stack.

Vulnerability

CVE-2026-23446 is a deadlock vulnerability in the Linux kernel's aqc111 USB Ethernet driver. The root cause is that the aqc111_suspend callback calls PM (Power Management) variants of its write command routines (e.g., aqc111_write32_cmd), which internally invoke usb_autopm_get_interface and pm_runtime_resume_and_get. During system suspend, the USB device's runtime status is already RPM_SUSPENDING, so calling rpm_resume on the parent device leads to an unresolvable wait, causing a task hang [1].

Exploitation

An attacker with physical access to the USB port or the ability to trigger a system suspend on a machine with an attached AQC111-based USB Ethernet adapter can exploit this. No authentication is required beyond the ability to initiate a suspend cycle. The deadlock occurs during normal suspend operations, making it a reliable denial-of-service vector [1].

Impact

Successful exploitation results in a kernel-level task hang in rpm_resume. This blocks another task holding the `rtnl_lock, effectively locking up the entire networking stack. The system becomes unresponsive for network operations, leading to a denial of service (DoS). The CVSS v3 base score is 5.5 (Medium), reflecting the local attack vector and high availability impact [1].

Mitigation

The fix replaces the PM-aware write command calls with their _nopm variants, preventing the recursive PM operations during suspend. Patches have been applied to the Linux kernel stable branches; users should update to a kernel containing the fix (e.g., commits referenced in [1], [2], [3], [4]). No workaround is available other than applying the patch or avoiding suspend while the device is connected.

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

10
  • Linux/Kernel10 versions
    cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*+ 9 more
    • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*range: >=5.0.1,<5.10.253
    • cpe:2.3:o:linux:linux_kernel:5.0:-:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
    • cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*
    • (no CPE)

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

8

News mentions

0

No linked articles in our index yet.