# CVE-2026-23446: net: usb: aqc111: Do not perform PM inside suspend callback

CVE-2026-23446 is fixed in 11 products on 1 platform, first by DEBIAN-CVE-2026-23446, released April 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-23446
- Priority: Routine
- CVSS: 5.5 (Moderate)
- EPSS: 0.0013
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Apr 3, 2026
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/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

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-azure sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-default sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.55.1.150700.17.33.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-livepatch-SLE15-SP7_Update_15 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-source sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.55.1 | [SUSE-SU-2026:2238-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-2238-1.md) | Jun 30, 2026 |
| Linux | linux Debian 12.15 (bookworm) | 6.1.170-1 | [DEBIAN-CVE-2026-23446](https://patchblox.com/security/data/fix/linux/debian-cve-2026-23446.md) | Apr 3, 2026 |
| Linux | linux Debian 13.5 (trixie) | 6.12.85-1 | [DEBIAN-CVE-2026-23446](https://patchblox.com/security/data/fix/linux/debian-cve-2026-23446.md) | Apr 3, 2026 |
| Linux | linux Debian 14 | 6.19.10-1 | [DEBIAN-CVE-2026-23446](https://patchblox.com/security/data/fix/linux/debian-cve-2026-23446.md) | Apr 3, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.