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

> A deadlock in the aqc111 USB network driver during suspend causes a system-wide networking stack lockup, requiring a kernel patch.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2026
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2026-23446, DEBIAN-CVE-2026-23446, GHSA-mqjm-rhm6-4854, ROOT-OS-DEBIAN-11-CVE-2026-23446, ROOT-OS-DEBIAN-12-CVE-2026-23446, ROOT-OS-DEBIAN-13-CVE-2026-23446, ROOT-OS-UBUNTU-2204-CVE-2026-23446, ROOT-OS-UBUNTU-2404-CVE-2026-23446, UBUNTU-CVE-2026-23446

## What is CVE-2026-23446?

CVE-2026-23446 is a medium-severity denial of service vulnerability in Linux kernel, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-23446?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-23446?

Apply the vendor's patch.

## Is CVE-2026-23446 being exploited?

There is no known exploitation of CVE-2026-23446 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23446 and fix it if it is affected.

What it is: CVE-2026-23446 is a medium-severity denial of service vulnerability in Linux kernel, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23446 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23446/ (Markdown: https://insights.sbomify.com/CVE-2026-23446/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23446
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23446
- OSV: https://osv.dev/vulnerability/CVE-2026-23446

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23446/
Summaries are generated and may contain mistakes; the official description above is the record.